public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/6410: Trouble with non-Ascii monetary symbols and wchar_t
Date: Mon, 06 May 2002 08:16:00 -0000	[thread overview]
Message-ID: <20020506151603.3804.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/6410; it has been noted by GNATS.

From: Paolo Carlini <pcarlini@unitus.it>
To: bkoz@gcc.gnu.org,  bkoz@gcc.gnu.org,  gcc-bugs@gcc.gnu.org, 
 gcc-prs@gcc.gnu.org,  nobody@gcc.gnu.org,  pcarlini@unitus.it, 
 gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/6410: Trouble with non-Ascii monetary symbols and wchar_t
Date: Mon, 06 May 2002 17:08:05 +0200

 bkoz@gcc.gnu.org wrote:
 
 >Synopsis: Trouble with non-Ascii monetary symbols and wchar_t
 >
 >Responsible-Changed-From-To: unassigned->bkoz
 >Responsible-Changed-By: bkoz
 >Responsible-Changed-When: Mon May  6 07:54:31 2002
 >Responsible-Changed-Why:
 >    Perhaps not really mine, but I'll pretend.
 >
 No, no... Definitely yours! ;-)
 
 >State-Changed-From-To: open->analyzed
 >State-Changed-By: bkoz
 >State-Changed-When: Mon May  6 07:54:31 2002
 >State-Changed-Why:
 >    According to Ulrich's comments here:
 >    http://gcc.gnu.org/ml/libstdc++/2002-04/msg00244.html
 >    
 >    One solution would be to setlocale to de_DE@euro, for instance, in your testcase.
 >    
 >    I tried that, and it didn't work really well. Here's the patch I'm currently using. I don't really like it, one because it breaks the current library API, and two because it's not MT-safe. I think something like this might be useful just to the testsuites can be cleaned up, and then a solution for glibc 2.3/uselocale can be used (which won't break the API for 3.1)
 >    
 >    Sound like a plan?
 >
 
 Excellent! If you could read in my mind you would find exactly that 
 reasoning!
 
 Please commit this, and I will finish cleaning up 
 22_locale/money_*_members.cc, as agreed, in the next few days.
 
 Thanks!
 Paolo.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6410
 
 


             reply	other threads:[~2002-05-06 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06  8:16 Paolo Carlini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-27  3:06 paolo
2002-07-03  9:13 bkoz
2002-05-13  5:56 Paolo Carlini
2002-05-06  7:54 bkoz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020506151603.3804.qmail@sources.redhat.com \
    --to=pcarlini@unitus.it \
    --cc=bkoz@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).