Re: Preprocessor Problem?

[linguist-gcc at rich-paul dot net]

On Sat, 27 May 2000, Zack Weinberg wrote:

> On Sat, May 27, 2000 at 11:23:33PM +0200, Martin v. Loewis wrote:
> > > I am attempting to port some c++ code that uses the following construct:
> > > 
> > > #define whatever(x) \
> > > class _whatever_x { \
> > >   void something() {} \
> > > }
> > 
> > > For some reason, it appears that gcc does not accept backslash
> > > escaped newlines in macro definitions?!?!?!
> > 
> > Sure it does. There is a chance that a Carriage Return character
> > follows the backslash, so there is whitespace after the backslash,
> > before the newline character.
> 
> ... in which case a development snapshot will work as expected.
> 
> zw
> 

Thank you both ... these files were indeed dragged from a dos machine, with
their damn line endings intact.

I'm also pleased to know that the new version ignores this ... I've always
thought that the best way to handle CR's in a text file was to ignore them
intirely ... this would tend to be the 'right thing' in most cases ... like
shell scripts and programs, and eliminate one source of DOS annoyance.