From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: dsb@prairienet.org,
"Daniel de Rauglaudre" <daniel.de_rauglaudre@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] sequence parser, revised syntax
Date: Tue, 10 Jul 2007 15:18:34 +0200 [thread overview]
Message-ID: <cd67f63a0707100618h15ab99bev4ffec2cd9c8de36b@mail.gmail.com> (raw)
In-Reply-To: <20070710092733.GB1266@yquem.inria.fr>
On 7/10/07, Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr> wrote:
> Hi,
Hi,
>
> On Mon, Jul 09, 2007 at 09:22:32AM -0500, dsb@prairienet.org wrote:
>
> > $ make stdlibr.cmo
> > ocamlc -pp "camlp4r pa_extend.cmo q_MLast.cmo" \
> > -I +camlp4 -c stdlibr.ml
> > File "stdlibr.ml", line 20, characters 40-48:
> > Unbound value Pcaml.sequence
> > make: *** [stdlibr.cmo] Error 2
FYI in ocaml 3.10...
> Some of the grammar sub-entries used in the files defining the syntax
> (e.g. "sequence") are indeed not accessible in the Pcaml module.
In 3.10 sequence is exported (so extensible).
> The problem is that there are many of them, many small entries useful
> only in specifics parts of the grammar.
In 3.10 most of them are exported.
> These small entries may change, appear, disappear, from a version of
> camlp4 to another when new things are added in the language syntax, or
> to fix possible bugs. It is often difficult to "standardize" them.
Even if it's difficult we tend to reach a stability point and then
prefer expose these things.
> Moreover, some of these entries may be used in revised syntax and not
> in normal syntax and vice-versa, or have a different type and semantics.
In 3.10 both syntaxes share a common grammar (the revised one),
therefore there are closer in types and semantics.
Cheers,
--
Nicolas Pouillard
prev parent reply other threads:[~2007-07-10 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 14:22 dsb
2007-07-10 9:27 ` [Caml-list] " Daniel de Rauglaudre
2007-07-10 13:18 ` Nicolas Pouillard [this message]
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=cd67f63a0707100618h15ab99bev4ffec2cd9c8de36b@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@inria.fr \
--cc=dsb@prairienet.org \
/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).