This is the mail archive of the
mailing list for the libstdc++ project.
Re: libstc++ expectations for newlib's string.h
- From: Joel Sherrill <joel dot sherrill at OARcorp dot com>
- Cc: Benjamin Kosnik <bkoz at redhat dot com>, jjohnstn at redhat dot com, eric dot norum at usask dot ca, newlib at sources dot redhat dot com, libstdc++ at gcc dot gnu dot org
- Date: Fri, 23 Aug 2002 12:31:32 -0500
- Subject: Re: libstc++ expectations for newlib's string.h
- Organization: OAR Corporation
- References: <50E9F2E2-B5F6-11D6-914D-00039366A118@usask.ca> <3D6549F6.196EB815@redhat.com> <3D66342C.8EFF7C1C@OARcorp.com> <email@example.com>
Benjamin Kosnik wrote:
> > > > I'd just like to add that the problem shows up in the C++ header
> > > > bits/locale_facets.tcc which uses strdup. This makes it impossible to
> > > > compile some otherwise-valid C++ programs with -ansi and the newlib
> > > > headers.
> Well, I think the problem is with libstdc++ and not newlib. Correctly
> nailing C89, C99, and the GNU extensions into namespaces has proven to
> be difficult. I think there is no reason for newlib to alter includes
> for this case based on __cplusplus.
newlib and glibc have different behaviors in this case. Are you saying
both are correct?
> Instead, this should probably be fixed in the C++ library.
Fair enough. I certianly won't argue that having so many somewhat
standards isn't confusing.
> > > `-ansi'
> > > In C mode, support all ANSI standard C programs. In C++ mode,
> > > remove GNU extensions that conflict with ISO C++.
> This is incorrect for GNU C++ post 3.0.x, as _GNU_SOURCE is defined in
> This is currently a low-to-medium priority issue.
:( Do you have a fix in mind for this particular case? Or a guiding
thought? We would be happy to try to fix the problems as we encounter
them if we knew what the rule of thumb was.