From: Sven M. H. <pe...@gm...> - 2001-03-22 20:24:28
|
On Thu, Mar 22, 2001 at 11:04:44AM -0700, Brian Paul wrote: > Karl Schultz wrote: > > __FUNCTION__ is a problem for Windows as well. > > > > It would be nice to have > > > > #if defined(VMS) || defined(WIN32) > > #define __FUNCTION__ > > #endif > > > > in texutil_tmp.h > > Better yet: > > #ifndef __FUNCTION__ > #define __FUNCTION__ "<some function>" > #endif As Antti mentioned, __FUNCTION__ is a gcc-builtin _variable_, not a preprocessor macro. Furthermore, shouldn't we rather check whether the compiler supports it at configure time? I guess there's a GCC for VMS, or not? Anyways, even a VMS or Win32 compiler might support __FUNCTION__, so it wouldn't be wise to just check for VMS/WIN32 being #define'd, but rather #define some other macro, in Make-config or by the configure script respectively and check that one. What do you think? -- @SVEN_M_HALLBERG@ <$(pesco_gmx.de)> "Would the All-Seeing Eye please look in my direction?" [ KeyID........: 0xC297FEAB ] [ Fingerprint..: FEA5 0F93 7320 3F39 66A5 AED3 073F 2D5F C297 FEAB ] |