From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28143 invoked by alias); 3 Apr 2003 15:46:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 28128 invoked by uid 71); 3 Apr 2003 15:46:00 -0000 Date: Thu, 03 Apr 2003 15:46:00 -0000 Message-ID: <20030403154600.28127.qmail@sources.redhat.com> To: jlquinn@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: =?iso-8859-1?Q?P=E9tur_Run=F3lfsson?= Subject: RE: libstdc++/9828: Regression: Segmentation fault in num_put::put Reply-To: =?iso-8859-1?Q?P=E9tur_Run=F3lfsson?= X-SW-Source: 2003-04/txt/msg00093.txt.bz2 List-Id: The following reply was made to PR libstdc++/9828; it has been noted by GNATS. From: =?iso-8859-1?Q?P=E9tur_Run=F3lfsson?= To: "Jerry Quinn" , , , , Cc: Subject: RE: libstdc++/9828: Regression: Segmentation fault in num_put::put Date: Thu, 3 Apr 2003 15:36:27 -0000 Jerry Quinn wrote: > Another is that locales carry the cache info to avoid this problem. I think this might be the best solution; it is very common to create a stringstream just to format one number (see for example boost::lexical_cast or operator<<(ostream&, complex&)). Storing the cache in the locale would allow such code to take advantage of the caches. It should be easy to implement this using the same techniques as are used for storing facets in locales. Regards, Petur