Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
Subject: RE: TEXT mode, BINARY mode default file opening
Date: Mon, 24 Jan 2005 18:39:17 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <41F4E1EA.8030505@familiehaase.de>
Message-ID: <NUTMEGYAPNXRPmcarcR00000032@NUTMEG.CAM.ARTIMI.COM>

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