caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] sequence parser, revised syntax
Date: Tue, 10 Jul 2007 11:27:33 +0200	[thread overview]
Message-ID: <20070710092733.GB1266@yquem.inria.fr> (raw)
In-Reply-To: <47259.192.17.3.107.1183990952.squirrel@mail.prairienet.org>

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

Some of the grammar sub-entries used in the files defining the syntax
(e.g. "sequence") are indeed not accessible in the Pcaml module.

The problem is that there are many of them, many small entries useful
only in specifics parts of the grammar.

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.

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.

The solution is to rewrite, yourself, the missing entry in your sources.
You can see how "sequence" is implemented in the revised syntax and copy
it (it is short).

Perhaps the function Grammar.Entry.print should show differently the
"accessible" entries and the "non accessible" ones. I am going to see
if it is possible to implement that.

-- 
Daniel de Rauglaudre
http://pauillac.inria.fr/~ddr/


  reply	other threads:[~2007-07-10  9:27 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 ` Daniel de Rauglaudre [this message]
2007-07-10 13:18   ` [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=20070710092733.GB1266@yquem.inria.fr \
    --to=daniel.de_rauglaudre@inria.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;
as well as URLs for NNTP newsgroup(s).