From: skaller <skaller@ozemail.com.au>
To: Alain.Frisch@ens.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Camlp4 integration
Date: 05 Oct 2003 06:33:13 +1000 [thread overview]
Message-ID: <1065299593.12873.8.camel@pelican> (raw)
In-Reply-To: <Pine.SOL.4.44.0310041323540.11019-100000@clipper.ens.fr>
On Sat, 2003-10-04 at 21:29, Alain.Frisch@ens.fr wrote:
> On 4 Oct 2003, skaller wrote:
>
> > Just some notes on camlp4. One problem I have noticed
> > is that camlp4'd codes don't work so well with other
> > tools such as ocamldep and ocamldoc. Both these programs
> > parse Ocaml but can't load camlp4 to do the job.
> > [I think you have to use pr_o.cmo to print a standard
> > Ocaml file to use them?]
>
> Both ocamldep and ocamldoc accept the -pp argument.
It isn't not documented?
> Sometimes, it would be
> more convenient to specify the syntax extensions directly in the Caml
> sources.
Yes, i think that would be nice.
There's a related issue for C++ where some discussion of
a directive:
#language "iso-9988"
or whatever so extensions in the next version don't
break existing codes (mainly by some identifiers becoming keywords).
-------------------
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
next prev parent reply other threads:[~2003-10-04 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 17:11 [Caml-list] ANNOUNCE: OCaml and XML (OX v0.1) didier plaindoux
2003-10-04 3:16 ` [Caml-list] Camlp4 integration skaller
2003-10-04 11:29 ` Alain.Frisch
2003-10-04 20:33 ` skaller [this message]
2003-10-06 8:45 ` Olivier Andrieu
2003-10-07 10:19 ` Alain.Frisch
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=1065299593.12873.8.camel@pelican \
--to=skaller@ozemail.com.au \
--cc=Alain.Frisch@ens.fr \
--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