This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: ieee_1003.1-2001 locale?
- From: jtc at acorntoolworks dot com (J.T. Conklin)
- To: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Thu, 24 Jun 2004 19:35:31 -0700
- Subject: Re: ieee_1003.1-2001 locale?
- References: <200406172109.i5HL9wru066702@latour.rsch.comm.mot.com>
- Reply-to: jtc at acorntoolworks dot com
Loren James Rittle <rittle@latour.rsch.comm.mot.com> writes:
>> Is the ieee_1003.1-2001 locale support intended to work, or is it just
>> a placeholder? I tried configuring gcc-3_3-branch with it enabled it
>> on a NetBSD/i386 machine (mostly for NLS message catalog support), but
>> it the compile failed because _GLIBCPP_NUM_CATEGORIES was not defined.
>
> Zero configurations use it by default thus the current bit rot. If
> you got it working on mainline, then the patch would be acceptable
> without much question. Here was the status on "20 Feb 2003":
Thanks. There is enough bitrot I think the best way to start is to
copy generic/* over ieee1003.1-2001/* and then work to add back the
locale support bit by bit. Adding message catalog support was easy; I
haven't yet had a chance to look at what it will take to restore the
character set conversion that was lost in the process. Considering it
didn't even build before, it's a big step forward.
I believe this will result in a substantial amount of duplicate code
between generic/* and ieee1003.1-2001/*. I wonder if it might be
preferable to have some conditionals in the generic code. Changes for
adding NLS-style message catalog support were only about 100 lines, or
~40 changed, easily conditionalized, lines out of ~1600. This may
help reduce the problem caused by it not being used by any target
configuration. I'll have to see whether this still holds true after
the work is complete.
--jtc
--
J.T. Conklin