Re: [Mesa3d-dev] Re: [Mesa3d-users] configure problem (was Missing GLX extensions)

[Keith W. <ke...@va...>]

Brian Paul wrote:
> 
> Karl Schultz wrote:
> >
> > > -----Original Message-----
> > > From: Sven M. Hallberg [mailto:pe...@gm...]
> > > Sent: Wednesday, March 21, 2001 9:37 AM
> > > To: Dirk Reiners
> > > Cc: Brian Paul; RC; mes...@li...
> > > Subject: [Mesa3d-dev] Re: [Mesa3d-users] configure problem
> > > (was Missing
> > > GLX extensions)
> >
> > snip
> >
> > > > > Well, if the compiler doesn't support the feature the
> > > only way would be
> > > > to use
> > > > > some sort of preprocessor kludge or hard-code the
> > > function names. Both
> > > > options
> > > > > seem kind of hard to accept. I'd say we check for the
> > > feature and in
> > > > case it's
> > > > > not available #define __FUNCTION__ to something sensable
> > > expressing the
> > > > lack.
> > > >
> > > > It does support __FILE__ and __LINE__, maybe using these
> > > would be better
> > > > than not having any indications of the problem happened.
> > >
> >
> > __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

I don't thing __FUNCTION__ is defined outside of functions, even in gcc.  

As much as I like and value __FUNCTION__ for working with templates, I'm
tempted to say we shouldn't allow it into CVS.

Keith