From: tmp123 <tmp123@menta.net>
To: caml-list@inria.fr
Subject: camlp4, camlp5... documentation clarification posible?
Date: Fri, 09 Nov 2007 11:22:13 +0000 [thread overview]
Message-ID: <473442E5.3030504@menta.net> (raw)
Hello,
With the maximum respect to the excelent job done by ocaml developers
and community, can I suggest to write, in an easy to find place, an
small clarification about what is camlp4, camlp5 and their main
"variants" (pre 3.10, post 3.10, PreCast, ...)? . Even in the
"Documentation" page at Inria's main web. A few lines could be enough.
Lots of persons, first, tries to decides what to use or the alternatives
more preferable, and after learns it.
I've not found a short way. With the current situation it is a few
dificult to known that camlp4 is a "newer syntax" version than camlp5,
the main "variants" of the camlp4, the main variants in its usage, ... .
It is necessary to read the camlp4 (pre 3.10) manual from Documentation,
the info at wiki for camlp4 (post 3.10) and the www of the camlp5 ...
only to known what is what.
Agains, just a sugestion.
Thanks.
reply other threads:[~2007-11-09 10:27 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=473442E5.3030504@menta.net \
--to=tmp123@menta.net \
--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