From: "Stuart Summerville (NEC)" <stuarts@icpdd.neca.nec.com.au>
To: <gcc@gcc.gnu.org>
Subject: Re: cpp w/DOS line feeds
Date: Thu, 09 Dec 1999 01:37:00 -0000 [thread overview]
Message-ID: <006b01bf4228$ea4552c0$cb884c93@porpoise.icpdd.neca.nec.com.au> (raw)
Hi all,
I'm currently 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. I've seen the informative thread from 21-Jan-99 about
this, with some bandied solutions, but nothing since then. Couldn't find
much in the gcc-bugs or gcc-announce lists either.
So, whats the current status on this issue? I'm currently running gcc
V2.91.57, & hope that 2.95.x contains the fix. Speaking of which, is the CPP
actually part of the gcc package? If not, where is it located? How does one
find out the version of their CPP tool?
Also, how does one search through web-based release notes between V2.91 and
V2.95 looking for such things?
Regards, sTu.
_________________________________________________________________________
Stuart Summerville NEC Australia Pty. Ltd.
ph: (+61 3) 9264-3090 Integrated Comm Products (R&D)
fax:(+61 3) 9264-3841 649-655 Springvale Road
e-mail: stuarts@icpdd.neca.nec.com.au Mulgrave, VIC 3170, AUSTRALIA
WARNING: multiple messages have this Message-ID
From: "Stuart Summerville (NEC)" <stuarts@icpdd.neca.nec.com.au>
To: <gcc@gcc.gnu.org>
Subject: Re: cpp w/DOS line feeds
Date: Fri, 31 Dec 1999 23:54:00 -0000 [thread overview]
Message-ID: <006b01bf4228$ea4552c0$cb884c93@porpoise.icpdd.neca.nec.com.au> (raw)
Message-ID: <19991231235400.4iaiNqPc3Hl6GDBhTA8eM3t4iNijaq8dYLa8EG4QrI4@z> (raw)
Hi all,
I'm currently 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. I've seen the informative thread from 21-Jan-99 about
this, with some bandied solutions, but nothing since then. Couldn't find
much in the gcc-bugs or gcc-announce lists either.
So, whats the current status on this issue? I'm currently running gcc
V2.91.57, & hope that 2.95.x contains the fix. Speaking of which, is the CPP
actually part of the gcc package? If not, where is it located? How does one
find out the version of their CPP tool?
Also, how does one search through web-based release notes between V2.91 and
V2.95 looking for such things?
Regards, sTu.
_________________________________________________________________________
Stuart Summerville NEC Australia Pty. Ltd.
ph: (+61 3) 9264-3090 Integrated Comm Products (R&D)
fax:(+61 3) 9264-3841 649-655 Springvale Road
e-mail: stuarts@icpdd.neca.nec.com.au Mulgrave, VIC 3170, AUSTRALIA
next reply other threads:[~1999-12-09 1:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 1:37 Stuart Summerville (NEC) [this message]
1999-12-09 8:13 ` Dave Brolley
1999-12-31 23:54 ` Dave Brolley
1999-12-31 23:54 ` Stuart Summerville (NEC)
-- strict thread matches above, loose matches on Subject: below --
1999-12-09 5:42 N8TM
1999-12-09 21:28 ` Per Bothner
1999-12-31 23:54 ` Per Bothner
1999-12-31 23:54 ` N8TM
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='006b01bf4228$ea4552c0$cb884c93@porpoise.icpdd.neca.nec.com.au' \
--to=stuarts@icpdd.neca.nec.com.au \
--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).