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
From: kumarchi AT comcast DOT net
To: "Max Bowsher" <maxb AT ukf DOT net>
Cc: <cygwin AT cygwin DOT com>
Subject: Re: bug in gcc3.3.1
Date: Thu, 04 Dec 2003 13:38:30 +0000
Message-Id: <120420031338.23374.1a10@comcast.net>
X-Authenticated-Sender: a3VtYXJjaGlAY29tY2FzdC5uZXQ=
Note-from-DJ: This may be spam

what was the reason for dropping the support?
( I have to now fix few lines of code!!)

thanx for the quick response
> kumarchi AT comcast DOT net wrote:
> > hello:
> > 
> > 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. 
> > 
> > has anybody else noticed this?
> 
> It's not a bug.
> 
> Multi line string literals have been deprecated in gcc 3.0, 3.1 and 3.2.
> Support was finally removed in 3.3.
> 
> Max.
> 

--
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/