Skip to Content.
Sympa Menu

freetds - RE: [freetds] __func__ vs. __FUNCTION__

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'ark AT eltex.net'" <ark AT eltex.net>, 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Cc:
  • Subject: RE: [freetds] __func__ vs. __FUNCTION__
  • Date: Mon, 27 Oct 2003 10:05:48 -0500

> From: ark AT eltex.ru [mailto:ark AT eltex.ru]
> Sent: October 27, 2003 9:08 AM
>
> 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.
:-/

--jkl

> > __FUNCTION__ or __func__, we'll have to tolerate compilers
> that don't have
> > them. Maybe something like:
> >
> > #ifndef __func__
> > # ifdef __FUNCTION__
> > # define __func__ __FUNCTION__
> > # else
> > # define __func__ __FILE__
> > # endif
> > #endif
-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page