------- Comment #5 from malitzke at metronets dot com 2006-05-10 14:43 -------
To A Pinski
While I am _not_ a C lawyer, the following seems pertinent:
1 __FUNCTION__ is _not_ a predefined macro. However __func__ a predefined
identifier and I will take this up with the kernel people. However, even
changing__FUNCTION__ to __func__ still produces an error. Let the language
lawyer sort this out.
2 Taking __FUNCTION__ entirely out of the original Macro Definition and using
all of the kernel paraphernalia produces valid code. Out of that context I can
not get even __FILE__ to work properly; only __line__
3 Your "Hi" misses the point because it is certainly not a predefined macro
and not even a predefined identifier. Therefore the comparison seems invalid to
me.
I am reopening this because I believe that the raised by "__func__" should be
addressed. Also it is not the first time that the kernel people found ways to
get GCC closer to the standards.
--
malitzke at metronets dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at gcc dot gnu dot org
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27528
