From: pavenis AT lanet DOT lv
To: "Rafal 'Raf256' Maj" <rafal AT raf256 DOT com>, djgpp AT delorie DOT com
Date: Tue, 18 Jun 2002 14:44:07 +0300
MIME-Version: 1.0
Subject: Re: bugs in gcc 3.1
Message-ID: <3D0F4737.12754.BF5ECD@localhost>
In-reply-to: <Xns92305933B2Braf256com@213.180.128.20>
X-mailer: Pegasus Mail for Windows (v4.01)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 16 Jun 2002 at 21:58, Rafal 'Raf256' Maj wrote:

> This are possible bugs in DJGPP basing on GCC 3.1
> 
> '\n\n' is compiled instead of give warning about multicharacter constant

If it's really so, then submitting bug to GNATS would be recommended.
See http://gcc.gnu.org/bugs.html for details.
 
> Imho ther are some problems with istrstream/strstream ::peek() did anyone 
> noticed them ?

Maybe. Cannot say anything more from so little information.

I have seen some strstream related messages about problems in gcc related
mailing lists.  I also suggest trying std::stringstream and related classes 
instead (strstream is deprecated)

Andris