quote:Original post by Matt Calabrese
If that is true, then what is the standards claim on polymorphism through "method pointers?"

quote:
Compilers should be free to their own implementation, but whether or not method pointers work with polymorphism should not.

quote:
What if you don''t want dynamic linking on an object through a method pointer call?

quote:Original post by _DarkWIng_
I''ve got a class and one of the functions takes as a parameter a function pointer. This works just fine if that function is some global one. But if it''s a member of another class the it just doesn''t work. Any idea how to solve this?


class Cubemap {
void RenderToCubemap( void (*renderFunction)(void) );
...
}

this works:
Cubemap cm
cm.RenderToCubemap( someGlobalFunction );

but this doesn''t
cm.RenderToCubemap( someOtherClass.publicFunction );


You should never let your fears become the boundaries of your dreams.

quote:Original post by SabreMan
(BTW, "method" is the incorrect terminology for C++).

quote:
Since the Standard has nothing to say about linking issues, I'll assume you mean dynamic despatch. If you don't want dynamic despatch, you don't make a function virtual.

  #include<iostream>class A{public:    virtual void Foo() { std::cout << "Parent\n"; }};class B    : public A{public:    virtual void Foo() { std::cout << "Child\n"; }};int main(){    B Something;    Something.A::Foo(); // This is what I'm refering to!                        // You explicitly call the 'A'                        // version of Foo, which is impossible                        // to do with member function pointers                        // because dynamic dispatch is assumed    return 0;}  

quote:Original post by Matt Calabrese
I''ve always been told to call them methods, and in all of the books I''ve read they call them methods.

quote:
What should I call them? Just member functions?

quote:
However -- you missed my point.

quote:Original post by philscott
In Java you call them methods and in C++ you call them functions. I seem to remember that calling member variables, attributes, is something that got introduced with Java as well.

quote:Original post by Matt Calabrese
I''ve never learned Java so I''m not picking it up from there, some sources that actually call them methods that I learned from are: C++ for Engineers and Scientists
by Gary J. Bronson; the online reference that so many people here refer to at http://www.parashift.com/c++-faq-lite/ and all of my teachers call them methods despite the fact that they don''t know java and have been in the industry for a very long time.

quote:
I think that saying "calling them methods is wrong in C++" is hogwash.

quote:
Maybe Java was the first language to call them that

quote:
but that''s how they''re often now referred to in C++.

quote:
From what I''ve seen, it''s an accepted term to use and it''s shorter than saying "member function." Arguing that it''s wrong to call them methods is just silly.