From: Christian Lindig <lindig@eecs.harvard.edu>
To: Vesa Karvonen <vesa.karvonen@housemarque.fi>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] On ocamlyacc and ocamllex
Date: Sun, 23 Sep 2001 16:09:15 -0400 [thread overview]
Message-ID: <20010923160915.B28129@lakeland.eecs.harvard.edu> (raw)
In-Reply-To: <000901c14466$7848e280$422aa8c0@housemarque.fi>; from vesa.karvonen@housemarque.fi on Sun, Sep 23, 2001 at 10:32:23PM +0300
On Sun, Sep 23, 2001 at 10:32:23PM +0300, Vesa Karvonen wrote:
> From: "Christian Lindig" <lindig@eecs.harvard.edu>
> I'd prefer that the lexer generator would be extended so that additional
> arguments could be added in a manner similar to this:
>
> rule token map = parse
> eof { P.EOF }
> | ws+ { token map lexbuf }
> | tab { tab map lexbuf; token map lexbuf }
> | nl { nl map lexbuf ; token map lexbuf }
> | nl '#' { line map lexbuf 0; token map lexbuf }
> ...
I lobbied for this three years ago and had a patch for ocamllex:
http://www.eecs.harvard.edu/~lindig/software/lex-patch.html
> Can this technique be used for adding context to parsers generated
> using ocamlyacc, too?
I'm not sure what you mean here. A Yacc parser works bottom up - do you
want to inject "context" into the tokens that are received from the
lexer?
> I agree that it may be somewhat easier for the parser generator, but I
> find that separating the token type definition from the grammar
> definition can be justified using quantitative technical arguments.
I agree that this alternative avoids the dependency of the type
definition on the grammar. But I am not sure that manually keeping the
type definition and the %token declarations in the parser in sync is
better than automatic recompiles or a little Make hack.
-- Christian
--
Christian Lindig Harvard University - DEAS
lindig@eecs.harvard.edu 33 Oxford St, MD 242, Cambridge MA 02138
phone: +1 (617) 496-7157 http://www.eecs.harvard.edu/~lindig/
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-09-23 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 21:09 Vesa Karvonen
2001-09-23 1:10 ` Christian Lindig
2001-09-23 16:27 ` Vesa Karvonen
2001-09-23 17:44 ` Christian Lindig
2001-09-23 19:32 ` Vesa Karvonen
2001-09-23 20:09 ` Christian Lindig [this message]
2001-09-23 20:51 ` Vesa Karvonen
2001-10-22 17:09 ` John Max Skaller
2001-10-22 16:47 ` John Max Skaller
2001-09-24 1:05 ` Christian RINDERKNECHT
2001-09-24 11:17 ` Vesa Karvonen
2001-10-22 17:24 ` John Max Skaller
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=20010923160915.B28129@lakeland.eecs.harvard.edu \
--to=lindig@eecs.harvard.edu \
--cc=caml-list@inria.fr \
--cc=vesa.karvonen@housemarque.fi \
/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