On Sat, Jul 13, 2002 at 12:26:07PM -0600, Eric Anholt wrote:
> Okay, this was my fault, I changed __FUNCTION__ to __func__ because gcc3
> complains about __FUNCTION__ being deprecated and I was told __func__
> was the portable alternative.  Maybe we need a #define __func__
> __FUNCTION__ for some gccs, but I don't understand why you are getting
> this and I'm not:

AFAIK __func__ is part of C-99 and __FUNCTION__ is a gcc extension.
With gcc3 they changed __FUNCTION__ to be the same as __func__. So
printf("foo " __FUNCTION__) is now wrong and instead you must use
printf("foo %s", __FUNCTION__).

-- 
Ville Syrjälä
[EMAIL PROTECTED]
http://www.sci.fi/~syrjala/


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to