Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: TEXT mode, BINARY mode default file opening
Date:	Mon, 24 Jan 2005 18:39:17 -0000
MIME-Version:	1.0
In-Reply-To:	<41F4E1EA.8030505@familiehaase.de>
Message-ID:	<NUTMEGYAPNXRPmcarcR00000032@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	24 Jan 2005 18:39:12.0140 (UTC) FILETIME=[FF6E24C0:01C50243]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Gerrit P. Haase
> Sent: 24 January 2005 11:54

> I never have any problems with any files, regardless which mode these
> files are.  GCC doesn't care if you use \r\n or \n as line ending.

  It does in at least one circumstance.  If you want to have a continued line,
by placing a backslash as the last character on the line, you *must* follow that
with a LF, not a CR, because the pre-processer understands an escaped LF as a
continuation, but has no idea what to do with a CR.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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