From: Issac Trotts <ijtrotts@ucdavis.edu>
To: caml-list@inria.fr
Subject: [Caml-list] camlidl and cpp
Date: Thu, 16 Oct 2003 01:50:19 -0700 [thread overview]
Message-ID: <20031016085019.GA16626@ucdavis.edu> (raw)
It would be handy if camlidl would pass a "-traditional-cpp"
flag to cpp by default. Here's an example on my Debian 3.0 box:
$ camlidl unix.idl
unix.idl:13:11: missing terminating " character
unix.idl:43:1: missing terminating " character
unix.idl:70:5: missing terminating " character
unix.idl:72:58: missing terminating " character
unix.idl:78:5: missing terminating " character
unix.idl:79:41: missing terminating " character
unix.idl:104:5: missing terminating " character
unix.idl:151:5: missing terminating " character
unix.idl: error during preprocessing
$ camlidl -prepro "cpp -traditional-cpp" unix.idl
The second way works just fine. Documenting this could prevent some
confusion.
Issac Trotts
--
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2003-10-16 8:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031016085019.GA16626@ucdavis.edu \
--to=ijtrotts@ucdavis.edu \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).