Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	"Krzysztof Duleba" <krzysan AT skrzynka DOT pl>
Subject:	Re: bug in gcc3.3.1
Date:	Wed, 3 Dec 2003 23:41:04 +0100
Lines:	20
Message-ID:	<bqlohr$n0l$1@sea.gmane.org>
References:	<120320032215 DOT 12429 DOT bc8 AT comcast DOT net>
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT org
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1165
Note-from-DJ:	This may be spam

kumarchi wrote:

> I found conssitent bug in gcc3.3.1
> 
> gcc2xx will compile the fiollwowing with no problem
> 
> printf (" ......
>          xxx ", ..)
> 
> where the format  "......
>          xxx " includes a new line character.
> 
> gcc3.3 will nto compile this and looks like it will allow
> an explicit new line inside.

You can even remove printf and leave only "..... 
..... " to get the same compile error.

Regards
Krzysztof Duleba


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -