Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Wed, 18 Oct 2000 16:10:34 -0400
To: cygwin AT sources DOT redhat DOT com
Subject: Re: Possible CRLF and -mno-cygwin bugs
Message-ID: <20001018161034.C5665@cygnus.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com
References: <20001018195101 DOT 18635 DOT qmail AT web110 DOT yahoomail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <20001018195101.18635.qmail@web110.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, Oct 18, 2000 at 12:51:01PM -0700

On Wed, Oct 18, 2000 at 12:51:01PM -0700, Earnie Boyd wrote:
>--- Mark Schoenberg <mark AT emmestech DOT com> wrote:
>>      After a rocky start, I have had reasonable success with Cygwin-1.1.4
>> (thanks to Chris Faylor for helping me get started).  I have, however, found
>> two
>> slight problems which I believe, if fixed, would enhance Cygwin.
>> 
>>      The first involves the old issue of carriage returns and line feeds:
>> Many
>> programs having ^Ms as the next-to-last character on a line compile just
>> fine.
>> However, I have noticed two problems.  The first is that in .c and .h files
>> "\^M^J" is not recognized as a continuation symbol as I believe it should be.
>> The second problem is that "#define FIRST Mark^M^J" defines "FIRST" as
>> "Mark^M",
>> whereas I think it should be defined as "Mark".
>> 
>
>Since there are many posts about \r\n and binary mode processing in the
>archives I'll only say that this is a user problem.

I'm not sure it's a user problem.  I'd say that this is really a gcc
problem, not a cygwin problem.  I've heard that this has been fixed in
recent versions of gcc.

For now, the only solution for the gcc that is shipped with cygwin is
"Don't do that."

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com