From: "Matthew D. Langston" <langston@SLAC.Stanford.EDU>
To: egcs <egcs@cygnus.com>
Subject: CRLF translations by CPP?
Date: Sun, 25 Jan 1998 21:35:00 -0000 [thread overview]
Message-ID: <34CC20B9.2DF560E0@SLAC.Stanford.EDU> (raw)
Quick Description
-----------------
Is there a mechanism to enable egcs to properly parse multi-line cpp
macros that end with Backslash-CarriageReturn-LineFeed instead of
Backslash-LineFeed?
Detailed Description
--------------------
I help develop a library written in C that is primarily developed under
WinNT, e.g. each line of the source code ends with a
CarriageReturn-LineFeed. The author of this library develops under
WinNT. I develop under Linux using egcs.
This library makes heavy use of multi-line cpp macros. Since this
library is developed under WinNT, these multi-line macros end with
Backslash-CarriageReturn-LineFeed instead of Backslash-LineFeed. This
prevents egcs from successfully compiling the source files in the
library which use multi-line cpp macros.
Is there a way to enable egcs to properly parse files with lines ending
in CarriageReturn-LineFeed? I was hoping for a solution that didn't
require me to use the `dos2unix' program (or an equivalent program) on
all of the source files of the library every time I receive patches to
the library source code.
--
Matthew D. Langston
SLD, Stanford Linear Accelerator Center
langston@SLAC.Stanford.EDU
next reply other threads:[~1998-01-25 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-25 21:35 Matthew D. Langston [this message]
1998-01-25 23:26 ` Per Bothner
1998-01-27 4:02 ` Bruno Haible
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=34CC20B9.2DF560E0@SLAC.Stanford.EDU \
--to=langston@slac.stanford.edu \
--cc=egcs@cygnus.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).