caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mitya Lomov <dsl@tepkom.ru>
To: caml-list@inria.fr
Subject: [Caml-list] Documenting CamlP4 syntax extensions
Date: Sat, 02 Mar 2002 13:59:37 +0400	[thread overview]
Message-ID: <3C80A289.D5B49C88@tepkom.ru> (raw)

Hello,

As I am heading to the release of Dynamic Caml 0.2,
it occurred to me that syntax extensions included there
grew quite complex, and will certainly require some
good deal of documenting to be released to the public.

It will be nice to be able to document camlp4 syntax
extensions in the same way as one documents his .mli
file...

The first step to that will be, I guess, some kind of
tool that is able to extract plain grammar definitions
(like BNF) from CamlP4 sources (just rules, without
semantics).

I see two ways to write such a tool: either reimplement
pa_extend.ml extensions so that they will output grammar
entries in readable form instead of adding them into CamlP4
internals, or some kind of "dummy syntax extension" module
which will dump internal CamlP4 grammar entries
in readable form.

The latter way is, to some extent, more clean - one does not
reimplement parsing (and do not need to reinvent
internal representation for grammars...). However, it is
possible that the first way is more extensible (say, if one
wants to add some fancy comments to syntax extensions, so
that the whole documentation is generated from source, then
it is easier to do that while parsing).

Any opinions? Probably such a beast already exists?

Regards,
Dmitry

-------------------
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:[~2002-03-02 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-02  9:59 Mitya Lomov [this message]
2002-03-02 11:35 ` Daniel de Rauglaudre
2002-09-13 18:15   ` Mitya Lomov
2002-09-14  2:51     ` Daniel de Rauglaudre

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=3C80A289.D5B49C88@tepkom.ru \
    --to=dsl@tepkom.ru \
    --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).