Edit Question - KnowledgeHub

Title Body

When I use the __FUNCTION__ macro/variable to print out debugging information, there seems to be a difference in what it outputs when using the Microsoft C++ compiler and gcc. For example, using the following trivial code: class Foo { public: void Bar(int a, int b, int c) { printf ("__FUNCTION__ = %s\n", __FUNCTION__); } }; int main (void) { Foo MyFoo; MyFoo.Bar(); return 0; } Using the Microsoft Visual C++ compiler, I get __FUNCTION__ = Foo::Bar whereas when compiling using gcc (in this case on the Mac), I get __FUNCTION__ = Bar The second example is not ideal because I quite often have several classes with, say, Init() and Uninit() methods and in a debug output trace its virtually impossible to tell which one of these has been called as the class name will be missing. Now, I know you can use the __PRETTY_FUNCTION__ in place of __FUNCTION__ to get something like __PRETTY_FUNCTION__ = void Foo::Bar(int, int, int) Which is fine, but its a bit too verbose for what I need and gets a bit long for functions with a lot of parameters. So my question is (at last), is there any way to get the output to look like simply Foo::Bar using gcc, as in the example above?

Tags (comma-separated) Cancel