From: John Max Skaller <skaller@maxtal.com.au>
To: Christian Lindig <lindig@eecs.harvard.edu>
Cc: Vesa Karvonen <vesa.karvonen@housemarque.fi>,
Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] On ocamlyacc and ocamllex
Date: Tue, 23 Oct 2001 03:09:38 +1000 [thread overview]
Message-ID: <3BD452D2.4FCEA1A9@maxtal.com.au> (raw)
In-Reply-To: <20010923160915.B28129@lakeland.eecs.harvard.edu>
Christian Lindig wrote:
> > 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.
Adding the tokens to the .mly file is a pain.
I have two other files which also need to list all tokens:
one to print them, and one to extract the source file/line/column
information. Both have to be manually tracked anyhow.
Worse, the %token command makes a normal union: how to use
polymorphic variants instead?
Even worse, the lexer and parser are improperly connected,
with the parser incorrectly taking a lexer and lexbuf as
arguments -- a right pain if you want to preprocess the
tokens. I have to create a dummy lexbuf/lexer to drive
the parser. The parser should take a callback function
as an argument. A patch to make this alternative calling
technique available would be useful.
--
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
New generation programming language Felix http://felix.sourceforge.net
Literate Programming tool Interscript
http://Interscript.sourceforge.net
-------------------
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-10-22 17:10 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
2001-09-23 20:51 ` Vesa Karvonen
2001-10-22 17:09 ` John Max Skaller [this message]
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=3BD452D2.4FCEA1A9@maxtal.com.au \
--to=skaller@maxtal.com.au \
--cc=caml-list@inria.fr \
--cc=lindig@eecs.harvard.edu \
--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;
as well as URLs for NNTP newsgroup(s).