From: Jan Rehders <cmdkeen@gmx.de>
To: caml-list@yquem.inria.fr
Subject: Reloaded syntax documentation?
Date: Tue, 6 Nov 2007 00:22:54 +0100 [thread overview]
Message-ID: <1F545F4E-9723-4864-84E9-C93E2750DE46@gmx.de> (raw)
Hi,
> As for original vs. revised syntax, I'm partial to the original
> syntax, but only because that's how I learned. The error messages it
> produces are problematic, however. I do like the "reloaded" syntax
> included with 3.10 that is basically original syntax with "end" after
> various constructs.
this inspired me to dig a bit in $install_path/lib/camlp4. Several
file names sound pretty interesting (mostly the reloaded syntax but
also stuff with sexy names like CamlP4ExceptionTracer, CamlP4Profiler
etc.). I had a look in the manual and the camlp4 wiki at [1] but
could not found too much documentation about them. Neither could I
figure out how to convert a regular syntax file into reloaded syntax
using camlp4, there appears to be no printer for it.
So am I stuck to dig into the sources? Is there any documentation
available for the reloaded syntax and the other stuff in the camlp4
directory?
greetings,
Jan
next reply other threads:[~2007-11-05 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 23:22 Jan Rehders [this message]
2007-11-06 10:27 ` [Caml-list] " Nicolas Pouillard
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=1F545F4E-9723-4864-84E9-C93E2750DE46@gmx.de \
--to=cmdkeen@gmx.de \
--cc=caml-list@yquem.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