Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <007301c3b9ee$a1558fc0$78d96f83@starfruit> From: "Max Bowsher" To: , References: <120320032215.12429.bc8@comcast.net> Subject: Re: bug in gcc3.3.1 Date: Wed, 3 Dec 2003 22:41:44 -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@comcast.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/