freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "ZIGLIO Frediano" <Frediano.Ziglio AT vodafone.com>
- To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
- Subject: RE: [freetds] __func__ vs. __FUNCTION__
- Date: Wed, 29 Oct 2003 15:51:44 +0100
> >
> > 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] __func__ vs. __FUNCTION__,
Craig A. Berry, 10/26/2003
-
Re: [freetds] __func__ vs. __FUNCTION__,
James K. Lowden, 10/27/2003
- Re: [freetds] __func__ vs. __FUNCTION__, ark, 10/27/2003
- <Possible follow-up(s)>
- RE: [freetds] __func__ vs. __FUNCTION__, Lowden, James K, 10/27/2003
- RE: [freetds] __func__ vs. __FUNCTION__, ZIGLIO Frediano, 10/29/2003
-
Re: [freetds] __func__ vs. __FUNCTION__,
James K. Lowden, 10/27/2003
Archive powered by MHonArc 2.6.24.