Migrating C++ source from Microsoft Windows NT to SCO Unix

Alexandre Oliva aoliva@redhat.com
Thu Mar 29 23:26:00 GMT 2001

On Mar 29, 2001, Craig Rodrigues <rodrigc@mediaone.net> wrote:

> On Thu, Mar 29, 2001 at 04:57:57PM +1200, Ross Smith wrote:
>> Craig Rodrigues wrote:
>> > 
>> > On Thu, Mar 29, 2001 at 11:19:49AM +1000, Timothy_Ko@nag.national.com.au wrote:
>> > >
>> > > 2.   NabString.h:594: macro `isalnum' used without args
>> > >
>> > >      where we declare as:
>> > >      virtual const bool NabString::isalnum() const;
>> > 
>> > isalnum() may be implemented as a macro in ctype.h, so implementing
>> > it yourself as a function could be a problem.
>> In C++ it's required to be a function, and having a class member
>> function with the same name is legal.

> This is a glibc vs. gcc (C++) issue.

Not really.  It's a libstdc++ issue.  libstdc++-v3's wrapper headers
#undef C functions that may be #defined as macros in the system
headers.  So this problem might be fixed in development snapshots.  I
haven't verified that it does that for isalnum, though.

Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

More information about the Libstdc++ mailing list