Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <003901c3ba6d$2c18cbd0$78d96f83@starfruit> From: "Max Bowsher" To: Cc: References: <120420031338 DOT 23374 DOT 1a10 AT comcast DOT net> Subject: Re: bug in gcc3.3.1 Date: Thu, 4 Dec 2003 13:47:32 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ X-Cam-AntiVirus: No virus found X-Cam-SpamDetails: Not scanned Note-from-DJ: This may be spam kumarchi AT comcast DOT net wrote: > what was the reason for dropping the support? > ( I have to now fix few lines of code!!) I don't know. The answer is probably somewhere in the gcc mail archives. Anyway, this is no longer a Cygwin question, so somewhat off-topic here. Max. > > 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/