public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Odd compiler error....please help
@ 1999-10-22 10:48 jay
  1999-10-22 13:24 ` Johnny Favorite
  1999-10-31 13:57 ` jay
  0 siblings, 2 replies; 4+ messages in thread
From: jay @ 1999-10-22 10:48 UTC (permalink / raw)
  To: help-gcc

When compiling files with multi-lined #defines, I noticed that the
compiler gives me errors for hidden characters e.g. space, tab, return,
even though I have the continue line symbol there "\".

Does anyone know how to get rid of this behavior?

Thanks.


* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Odd compiler error....please help
  1999-10-22 10:48 Odd compiler error....please help jay
@ 1999-10-22 13:24 ` Johnny Favorite
  1999-10-31 13:57   ` Johnny Favorite
  1999-10-31 13:57 ` jay
  1 sibling, 1 reply; 4+ messages in thread
From: Johnny Favorite @ 1999-10-22 13:24 UTC (permalink / raw)
  To: help-gcc

jay wrote:
> When compiling files with multi-lined #defines, I noticed that
> the compiler gives me errors for hidden characters e.g. space,
> tab, return, even though I have the continue line symbol
> there "\".
>
> Does anyone know how to get rid of this behavior?

I had something similar to that, I think, as I was porting some Win32 code
to GCC.  In DOS/Windows, text file lines end with CR/LF, but UNIX text files
(like GCC expects in my particular setup) end with just LF.  The only place
where this seemed to cause a problem was with the line continuation
character.

I changed the text files from having CR/LF line breaks to just LF line
breaks and everything was fine after that.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Odd compiler error....please help
  1999-10-22 10:48 Odd compiler error....please help jay
  1999-10-22 13:24 ` Johnny Favorite
@ 1999-10-31 13:57 ` jay
  1 sibling, 0 replies; 4+ messages in thread
From: jay @ 1999-10-31 13:57 UTC (permalink / raw)
  To: help-gcc

When compiling files with multi-lined #defines, I noticed that the
compiler gives me errors for hidden characters e.g. space, tab, return,
even though I have the continue line symbol there "\".

Does anyone know how to get rid of this behavior?

Thanks.


* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Odd compiler error....please help
  1999-10-22 13:24 ` Johnny Favorite
@ 1999-10-31 13:57   ` Johnny Favorite
  0 siblings, 0 replies; 4+ messages in thread
From: Johnny Favorite @ 1999-10-31 13:57 UTC (permalink / raw)
  To: help-gcc

jay wrote:
> When compiling files with multi-lined #defines, I noticed that
> the compiler gives me errors for hidden characters e.g. space,
> tab, return, even though I have the continue line symbol
> there "\".
>
> Does anyone know how to get rid of this behavior?

I had something similar to that, I think, as I was porting some Win32 code
to GCC.  In DOS/Windows, text file lines end with CR/LF, but UNIX text files
(like GCC expects in my particular setup) end with just LF.  The only place
where this seemed to cause a problem was with the line continuation
character.

I changed the text files from having CR/LF line breaks to just LF line
breaks and everything was fine after that.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~1999-10-31 13:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-10-22 10:48 Odd compiler error....please help jay
1999-10-22 13:24 ` Johnny Favorite
1999-10-31 13:57   ` Johnny Favorite
1999-10-31 13:57 ` jay

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).