public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Watson <jwatson@stsci.edu>
To: help-gcc@gnu.org
Subject: DOS EOL in multiline #define
Date: Wed, 05 Jan 2000 16:46:00 -0000	[thread overview]
Message-ID: <3873C447.78441FE6@stsci.edu> (raw)

I am trying to compile a c program with gcc.
The c source file in in DOS format, so all the EOL's have
that extra annoying ^M.  Unfortunately, gcc craps out on
multiline #defines during the compile.

Is there any way to make gcc ignore the ^M's without
converting the source file to a sane format?


I tried using
#define ^M ""

but, gcc says that the ^M character is not a valid macro name.

Thanks,
JW

WARNING: multiple messages have this Message-ID

From: John Watson <jwatson@stsci.edu>
To: help-gcc@gnu.org
Subject: DOS EOL in multiline #define
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <3873C447.78441FE6@stsci.edu> (raw)
Message-ID: <20000401000000.B1piFyBGF8djQ8IOs4G3A-Qo8oixC9-a090edYEYPuA@z> (raw)

I am trying to compile a c program with gcc.
The c source file in in DOS format, so all the EOL's have
that extra annoying ^M.  Unfortunately, gcc craps out on
multiline #defines during the compile.

Is there any way to make gcc ignore the ^M's without
converting the source file to a sane format?


I tried using
#define ^M ""

but, gcc says that the ^M character is not a valid macro name.

Thanks,
JW

             reply	other threads:[~2000-01-05 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-05 16:46 John Watson [this message]
2000-01-06  8:50 ` John Watson
2000-04-01  0:00   ` John Watson
2000-04-01  0:00 ` John Watson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3873C447.78441FE6@stsci.edu \
    --to=jwatson@stsci.edu \
    --cc=help-gcc@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).