From: Zack Weinberg <zack@rabi.columbia.edu>
To: Joe Buck <jbuck@synopsys.com>
Cc: egcs@egcs.cygnus.com
Subject: Re: cpp w/DOS line feeds
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <199901211941.OAA20205@rabi.phys.columbia.edu> (raw)
Message-ID: <19990131235800.35Uw1qD2MV4pxcYvx00hCN3oT1-0L1_Yd5tUQ8hWH_k@z> (raw)
In-Reply-To: <199901211809.KAA04467@atrus.synopsys.com>
On Thu, 21 Jan 99 10:09:06 PST, Joe Buck wrote:
>
>> How does your patch handle lone CR? This should be handled as
>> a line-terminator as well. (Lone CR is used a line-terminator
>> on MacOS, plus a few other rare/obsolete OSes.) Therfore, just
>> throwing away CR does not do the Right Thing.
>
>Unix has \n, DOS/Windows has \r\n, Mac has \r. All three should be
>treated as if \n were typed.
I have experimental code for cpplib that makes it understand all three
possible line endings (and, coincidentally, trigraphs). I'm planning to
whip it into shape within the next few days.
zw
next prev parent reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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-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
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=199901211941.OAA20205@rabi.phys.columbia.edu \
--to=zack@rabi.columbia.edu \
--cc=egcs@egcs.cygnus.com \
--cc=jbuck@synopsys.com \
/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).