Subject: Re: Cygwin 1.1.3-1 (g++) parser not sure how to deal with continuation '\'
From: "Paul Garceau" <[email-masked]>
To: [email-masked], [email-masked]
Date: Tue, 1 Aug 2000 14:50:36 -0800

On 1 Aug 2000, at 8:48, the Illustrious 13mb80000-HallM(10053584)37x1 wrote:

> >    Example:
> > 
> > a) 
> > #define D3DRGB(r, g, b) \
> > 	(0xff000000L | ( ((long)((r) * 255)) << 16) | (((long)((g) *
> > 255)) << 8) 
> | (long)((b) * 255))
> > 
> > 	fails ("stray '\' in program").
> > 
> > b)
> > #define D3DRGB(r, g, b) (0xff000000L | ( ((long)((r) * 255)) <<
> > #16) | 
> (((long)((g) * 255)) << 8) | (long)((b) * 255))
> >       
> > 	works.
> > 
> 
> Almost certainly the backslash is followed by a <CR> character
> before the <LF> character.  Since you are reading the file in
> binary mode, cygwin does not change <CR><LF> into \n, so the
> backslash does not occur at the end of the line (it's got a
> whitespace character following it).  If you get rid of the <CR>s
> at the end of the lines, it should work correctly.

	Yes, thank you...what would a sed script look like to replace 
"<CR><LF>" with "\n" for about 14 header files?  I'm assuming 
there are no plans for adding the parser technology necessary to 
autoreplace <CR><LF> with "/n"; nor is there any simple way to 
make the replacement outside of sed.  Is this accurate?

	Thanks again,

		Paul G.

Nothing real can be threatened.
    Nothing unreal exists.

--
Want to unsubscribe from this list?
Send a message to [email-masked]