From: Per Bothner <per@bothner.com>
To: N8TM@aol.com
Cc: gcc@gcc.gnu.org
Subject: Re: cpp w/DOS line feeds
Date: Thu, 09 Dec 1999 21:28:00 -0000 [thread overview]
Message-ID: <m2k8mnz7ob.fsf@magnus.bothner.com> (raw)
In-Reply-To: <0.489ce69b.25810b85@aol.com>
N8TM@aol.com writes:
> In a message dated 12/9/99 1:38:24 AM Pacific Standard Time,
> stuarts@icpdd.neca.nec.com.au writes:
>
> > contemplating the problem in gcc (or cpp in particular) of
> > multi-line macros that are not interpreted properly if the EOL is made up
> of
> > CRs as well as LFs.
> >hope that 2.95.x contains the fix
>
> Don't hope too much. As mentioned in the earlier discussion, cpp is intended
> to be able to use any character preceded by backslash to stand for that
> character taken literally, in the old unix tradition.
Except of course for newline. And earlier discissions agreed that
CR-LF should be treated as equivalent to NL. In fact, I believe
this is the currently implemented behavior if you enable cpplib
as a replacement for the old cpp.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/
WARNING: multiple messages have this Message-ID
From: Per Bothner <per@bothner.com>
To: N8TM@aol.com
Cc: gcc@gcc.gnu.org
Subject: Re: cpp w/DOS line feeds
Date: Fri, 31 Dec 1999 23:54:00 -0000 [thread overview]
Message-ID: <m2k8mnz7ob.fsf@magnus.bothner.com> (raw)
Message-ID: <19991231235400.1jtmwHVXKk39n-PCmIR0zwymZSE1qL7RDdT-WozNmng@z> (raw)
In-Reply-To: <0.489ce69b.25810b85@aol.com>
N8TM@aol.com writes:
> In a message dated 12/9/99 1:38:24 AM Pacific Standard Time,
> stuarts@icpdd.neca.nec.com.au writes:
>
> > contemplating the problem in gcc (or cpp in particular) of
> > multi-line macros that are not interpreted properly if the EOL is made up
> of
> > CRs as well as LFs.
> >hope that 2.95.x contains the fix
>
> Don't hope too much. As mentioned in the earlier discussion, cpp is intended
> to be able to use any character preceded by backslash to stand for that
> character taken literally, in the old unix tradition.
Except of course for newline. And earlier discissions agreed that
CR-LF should be treated as equivalent to NL. In fact, I believe
this is the currently implemented behavior if you enable cpplib
as a replacement for the old cpp.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/
next prev parent reply other threads:[~1999-12-09 21:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 5:42 N8TM
1999-12-09 21:28 ` Per Bothner [this message]
1999-12-31 23:54 ` Per Bothner
1999-12-31 23:54 ` N8TM
-- strict thread matches above, loose matches on Subject: below --
1999-12-09 1:37 Stuart Summerville (NEC)
1999-12-09 8:13 ` Dave Brolley
1999-12-31 23:54 ` Dave Brolley
1999-12-31 23:54 ` Stuart Summerville (NEC)
1999-01-21 4:56 Matthew Kirkwood
1999-01-21 6:12 ` Matthias Urlichs
1999-01-21 6:18 ` Matthew Kirkwood
1999-01-31 23:58 ` Matthew Kirkwood
1999-01-21 9:33 ` Per Bothner
1999-01-21 10:09 ` Joe Buck
1999-01-21 11:41 ` Zack Weinberg
1999-01-23 3:24 ` Matthias Urlichs
1999-01-23 8:22 ` Per Bothner
1999-01-23 8:46 ` Matthias Urlichs
1999-01-31 23:58 ` Matthias Urlichs
1999-01-31 23:58 ` Per Bothner
1999-01-31 23:58 ` Matthias Urlichs
1999-01-31 23:58 ` Zack Weinberg
1999-01-31 23:58 ` Joe Buck
1999-01-23 3:21 ` Matthias Urlichs
1999-01-31 23:58 ` Matthias Urlichs
1999-01-31 23:58 ` Per Bothner
1999-01-31 23:58 ` Matthias Urlichs
1999-01-31 23:58 ` Matthew Kirkwood
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=m2k8mnz7ob.fsf@magnus.bothner.com \
--to=per@bothner.com \
--cc=N8TM@aol.com \
--cc=gcc@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).