This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Migrating C++ source from Microsoft Windows NT to SCO Unix
- To: Craig Rodrigues <rodrigc at mediaone dot net>
- Subject: Re: Migrating C++ source from Microsoft Windows NT to SCO Unix
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 30 Mar 2001 04:26:32 -0300
- Cc: Ross Smith <ross dot s at ihug dot co dot nz>, gcc at gcc dot gnu dot org
- Cc: libstdc++ at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <4A256A1E.00075EC8.00@naunb909.national.com.au><20010328204313.A19005@mediaone.net> <3AC2C0D5.CD2E839E@ihug.co.nz><20010329200938.B22096@mediaone.net>
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