From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18007 invoked by alias); 18 Nov 2002 04:16:07 -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 17966 invoked by uid 71); 18 Nov 2002 04:16:04 -0000 Date: Fri, 22 Nov 2002 14:27:00 -0000 Message-ID: <20021118041604.17962.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Phil Edwards Subject: Re: libstdc++/8616: std::string ? Reply-To: Phil Edwards X-SW-Source: 2002-11/txt/msg00863.txt.bz2 List-Id: The following reply was made to PR libstdc++/8616; it has been noted by GNATS. From: Phil Edwards To: bwheadley@earthlink.net Cc: gcc-gnats@gcc.gnu.org, nigels@nigels.com Subject: Re: libstdc++/8616: std::string ? Date: Sun, 17 Nov 2002 23:14:37 -0500 On Mon, Nov 18, 2002 at 12:57:47AM -0000, bwheadley@earthlink.net wrote: > >Description: > std::string j is a valid datatype? The second foo.log doesn't contain any compiler messages. In any case, no, this int main(int argc,char *argv[]) { std::string j; // j = 25.9; } is not going to work. I'm not even certain what you're trying to do. Phil -- I would therefore like to posit that computing's central challenge, viz. "How not to make a mess of it," has /not/ been met. - Edsger Dijkstra, 1930-2002