While looking at this macro, I noticed that it wasn't always necessarily
defined. That prompted me to search the current sources to make sure
that all uses were adequately protected, which they were. But to help
prevent future uses to be made unprotected, this patch expands the
current macro documentation a bit.
gdb/ChangeLog:
* common/common-utils.h (FUNCTION_NAME): Expand the macro's
documentation a bit.
+2014-01-22 Joel Brobecker <brobecker@adacore.com>
+
+ * common/common-utils.h (FUNCTION_NAME): Expand the macro's
+ documentation a bit.
+
2014-01-21 Roland McGrath <mcgrathr@google.com>
* configure.ac: Call AM_PROG_INSTALL_STRIP.
#include <stddef.h>
#include <stdarg.h>
-/* Version 2.4 and later of GCC define a magical variable `__PRETTY_FUNCTION__'
+/* If possible, define FUNCTION_NAME, a macro containing the name of
+ the function being defined. Since this macro may not always be
+ defined, all uses must be protected by appropriate macro definition
+ checks (Eg: "#ifdef FUNCTION_NAME").
+
+ Version 2.4 and later of GCC define a magical variable `__PRETTY_FUNCTION__'
which contains the name of the function currently being defined.
This is broken in G++ before version 2.6.
C9x has a similar variable called __func__, but prefer the GCC one since