[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freetds
Subject:    RE: [freetds] __func__ vs. __FUNCTION__
From:       "ZIGLIO Frediano" <Frediano.Ziglio () vodafone ! com>
Date:       2003-10-29 14:51:44
[Download RAW message or body]

> > 
> > IIRC, this won't work. __FUNCTION__ is not "real" defined 
> macro and it 
> > cannot be checked by #ifdef, at least gcc manual says so.
> 
> I see.  Quite right, as a simple test program shows:
> 
> #include <stdio.h>
> 
> int main()
> {
> #ifdef __FUNCTION__
>         char msg[] = "__FUNCTION__\n";
> #else
>         char msg[] = "no __FUNCTION__\n";
> #endif
>         puts(msg);
> }
> 
> Looks like a job for AC_TRY_COMPILE.  If we want to use the 
> feature at all. :-/
> 

IMHO replacing __func__/__FUNCTION__ manually with real function name is
the best solution...

freddy77
_______________________________________________
FreeTDS mailing list
FreeTDS@lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds

[prev in list] [next in list] [prev in thread] [next in thread]