From: Anton Moscal <msk@post.tepkom.ru>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Camlp4 3.01.4
Date: Thu, 24 May 2001 11:42:23 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.21.0105241129570.1137-100000@kouzdra.glokaya> (raw)
In-Reply-To: <20010521134328.C16047@verdot.inria.fr>
On Mon, 21 May 2001, Daniel de Rauglaudre wrote:
> Hello everybody,
>
> I made a release 3.01.4 for Camlp4, compatible with Ocaml 3.01.
>
> Main changes since Camlp4 3.01:
>
> - Added functions in module Token to create lexers:
> 1/ from char stream parser
> 2/ from ocamllex lexer
This is useful. But what do you think about incorporating in Camlp4 some
features from AntLR (successor of the PCCTS), such as:
parameterized rules: something like
rule [parameters list]: [[ ... ]]
and invoking by "rule [actual parameters list]"
predicates
(expression)? => rule,
parser try to parse "rule" only if "expression" true,
syntax predicates:
(rule1) => rule2: parser try to parse rule1, if succeed then parser
returns to initial position and try to parse rule2. rule1 usually is a
prefix of rule2, but without side effects
And the last, but not least:
Implements some explicit distinction beetween rule with side effects and
without it (for example - rule: ... and rule :: ... ). When rule without
side effects failed, parser can keeps trying other alternatives.
The last two features requires input streams with "reset to saved
position" function, but this shouldn't be a serious problem.
Best wishes,
Anton Moscal
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-05-25 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 11:43 Daniel de Rauglaudre
2001-05-21 11:45 ` [Caml-list] " Daniel de Rauglaudre
2001-05-24 7:42 ` Anton Moscal [this message]
2001-05-24 16:44 ` [Caml-list] " 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=Pine.LNX.4.21.0105241129570.1137-100000@kouzdra.glokaya \
--to=msk@post.tepkom.ru \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@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