From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5194 invoked by alias); 10 Oct 2002 06:15:21 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 5171 invoked from network); 10 Oct 2002 06:15:19 -0000 Received: from unknown (HELO thinkpad.c0202001.roe.itnq.net) (217.112.132.138) by sources.redhat.com with SMTP; 10 Oct 2002 06:15:19 -0000 Received: from karel (helo=localhost) by thinkpad.c0202001.roe.itnq.net with local-esmtp (Exim 3.35 #1 (Debian)) id 17zWbm-0001Uo-00; Thu, 10 Oct 2002 08:15:42 +0200 Date: Thu, 10 Oct 2002 08:10:00 -0000 From: Karel Gardas X-X-Sender: karel@thinkpad.c0202001.roe.itnq.net To: Benjamin Kosnik cc: gcc@gcc.gnu.org Subject: Re: basic_string linking related problem In-Reply-To: <20021009153045.5b3eab86.bkoz@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-10/txt/msg00540.txt.bz2 On Wed, 9 Oct 2002, Benjamin Kosnik wrote: > ... your link error is coming from an instantiation of > char_traits. This instantiation is not specified in the > C++ standard. Furthermore, using basic types to specialize standard > components, instead of user-defined types, is not legal. > OK, so I don't need to report anything into GNATS. > It is, however, a seemingly well-established practice. > > There has been a lot of discussion of this, mostly on Fridays during the > last two months on the libstdc++ list. If you search for this, you'll > find workarounds. > I'll look at it. Thanks, Karel -- Karel Gardas kgardas@objectsecurity.com ObjectSecurity Ltd. http://www.objectsecurity.com