--snip/snip
> > to kill the 3.x warning?
>
> Well, the warning (at least from what I've seen) is when you do:
> "In " __FUNCTION__ " something bad happened\n", which __func__ just
> won't do. Doing:
> "In %s something bad happened\n", __FUNCTION__
> Is OK[1].
from gcc3/Function-Names:
--------------
Note that these semantics are deprecated, and that GCC 3.2 will handle __FUNCTION__ and __PRETTY_FUNCTION__ the same way as __func__.
__func__ is defined by the ISO standard C99:
The identifier __func__ is implicitly declared by the translator
as if, immediately following the opening brace of each function
definition, the declaration
static const char __func__[] = "function-name";
appeared, where function-name is the name of the lexically-enclosing
function. This name is the unadorned name of the function.
By this definition, __func__ is a variable, not a string literal. In particular, __func__ does not catenate with other string literals.
--------------
which means, __FUNCTION__ will still be supported (gcc3.2), you just cannot
catenate it as it was the case before.
so Toms snipplet above should be ok for all versions of gcc which are
recommended today, and will also work with gcc3.2
tm
-- in some way i do, and in some way i don't.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:19 EST