Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <200005171902.NAA16268@chorus>
Date: Wed, 17 May 2000 13:02:06 -0600 (MDT)
From: "13mb80000-HallM(10053584)37x10" <marcus AT bighorn DOT dr DOT lucent DOT com>
Reply-To: "13mb80000-HallM(10053584)37x10" <marcus AT bighorn DOT dr DOT lucent DOT com>
Subject: Re: multi-line #defines 
To: cygwin AT sourceware DOT cygnus DOT com, mark AT emmestech DOT com
X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4m sparc 
Content-Type: text
X-Sun-Text-Type: ascii



>      The problem on my machine (Win98) was that the compiler didn't seem to
> recognize or like multiple line #defines, which could be found in files like
> reent.h, winnt.h, etc.  An error message of "stray \ in program" was 
generated.
> Removing the continuation back-slashes simply caused other error messages 
since
> the multi-line #define still was not recognized.  The solution on my machine
> was to remove both the "\" and the following linefeed, i.e. to create a long,
> but one-line #define. 
> 
>      Is this a problem for anyone but me?  Is there a patch/upgrade?  Is there
> a work-around?  I am nervous that other machines may not like the very long
> lines that I am using with my "fix".

I suspect that you have a text/binary mount point problem (or a related
one).  The file most likely has <CR><LF> terminations and the compiler is
reading it in binary mode, so it sees these terminations at the end of the
line.  Now, <CR> is counted as a whitespace character, so the compiler does
not usually get too upset by this, but if a #define is continued to the
next line with a '\', the compiler (actually the pre-processor) sees the
<CR> as the following character, not '\n', and it does not treat it as
a continuation.

marcus

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