Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Correnson Loïc" <Loic.Correnson@trusted-logic.fr>
To: <caml-list@inria.fr>
Subject: [Caml-list] Suggestions for OcamlDoc & CamlP4
Date: Tue, 2 Mar 2004 13:30:45 +0100	[thread overview]
Message-ID: <002301c40052$2f739a00$0203a8c0@hoedic> (raw)

Hye!
I have two little queries about these *beautiful* tools:

 + In ocamldoc, -stars option should also remove the starts at end of
comments, like in:
    (**
     * {1 Documentation}
     * Blablabla...
     **)

 +In camlp4, location of terminals are lost inside rule's actions. Actually,
this is a draw back of the
   token pattern-matching design, where the data returned from the lexer to
the parser is a string.
   The solution which consists in encapsulating a terminal inside a specific
rule (for which the
   location in known through [loc]) does work properly! This solution would
prevent
  the parser from factorizing  terminals inside rules, which drawn the
parsed language
  down to LL(0), if not worse.
  According to my point of view, a lexer should be able to define the result
of its matching function,
  while preserving the design of matching a couple of strings. More
precisely:

type 'a Token.glexer should be replaced by ('a,'b) glexer, where the pattern
function could be :
tok_match : pattern -> 'a -> 'b

then, the GLexerType could have the following signature:
type te (* input token *)
type td (* token's data for parser *)
val lexer : (te,td) Token.glexer

Of course, these are only suggestions.
    L.

-------------------
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:[~2004-03-02 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 12:30 Correnson Loïc [this message]
2004-03-05  8:52 ` Maxence Guesdon

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='002301c40052$2f739a00$0203a8c0@hoedic' \
    --to=loic.correnson@trusted-logic.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