This is the mail archive of the
libstdc++@sources.redhat.com
mailing list for the libstdc++ project.
langinfo.h on glibc-2.1.94
- To: stdc++ <libstdc++ at sourceware dot cygnus dot com>
- Subject: langinfo.h on glibc-2.1.94
- From: brent at rcfile dot org
- Date: Sat, 7 Oct 2000 16:26:33 -0400
Hi,
first off, kudos to Steven and Benjamin for the c header work :)
Now, compiling the library with glibc-2.1.94 I get an error when
including langinfo.h...
extern char *__nl_langinfo_l (nl_item __item, __locale_t l)
notes: the langinfo.h file is not in the _C_legacy namespace, so I
tried a shadow/langinfo.h,bits/wrap_langinfo.h approach, but the
enum{} containing CODESET was then not visible in bits/codecvt.h.
langinfo.h is included from bits/codecvt.h.
[/usr/include/langinfo.h]
562 #ifdef __USE_GNU
563 /* This interface is for the extended locale model. See <locale.h> for
564 more information. */
565
566 /* Get locale datatype definition. */
567 # include <xlocale.h>
568
569 /* Just like nl_langinfo but get the information from the locale object
570 extern char *__nl_langinfo_l (nl_item __item, __locale_t l);
571 #endif
is this interface to be used in libstdc++-v3? If not, maybe some
preprocessor work like this in bits/codecvt.h might be acceptable,
if not only _ugly as heck_
#ifdef __USE_GNU
#define __SAVE__USE_GNU __USE_GNU
#undef __USE_GNU
#endif
#include <langinfo.h>
#ifdef __SAVE__USE_GNU
#define __USE_GNU __SAVE__USE_GNU
#undef __SAVE__USE_GNU
#endif
if it is to be used, should the langinfo.h be shadowed? or should
we just make sure the __locale_t is visible in :: by the
__nl_langinfo_l function delcaration is encountered?
cheers,
brent
--
All opinions expressed are My own, unless otherwise attributed. In
presenting facts, I expressly reserve the right to be Wrong. Portions
of this message authored by Me are subject to the Free Thought License.