From: Ian T Zimmerman <itz@transbay.net>
To: caml-list@inria.fr
Subject: Re: Looking for a nail
Date: Tue, 26 Jan 1999 11:20:47 -0800 [thread overview]
Message-ID: <199901261920.LAA23249@kronstadt.transbay.net> (raw)
In-Reply-To: <199901252053.VAA21739@irritatie.cs.kun.nl> (message from Hendrik Tews on Mon, 25 Jan 1999 21:53:53 +0100)
> Date: Mon, 25 Jan 1999 21:53:53 +0100
> From: Hendrik Tews <tews@irritatie.cs.kun.nl>
> X-Gnus-Article-Number: 99 Tue Jan 26 11:02:09 1999
>
> 1. Bringing ocamletags to live again. I keep a copy, which compiles
> under 2.01 and reads 2.01 files, but does not create much tags for
> classes. I am willing to through this into the pool (if Francois
> Rouaix agrees).
An etags generator (written in Elisp) is part of current snapshot of
the Emacs subdirectory. It is exactly as precise/correct as the imenu
generator :-) If you want to see it and can't wait for next release,
write me.
> 2. The yacc and lex interface of ocaml could be a tuned up. Some
> ideas:
> - use a oo interface for lexers and parsers, this would provide a
> much butter way of adding state information to lexers and parsers
> [cf Christian Lindig's mail "Proposal for new Lexing Module (long)"
> from Mon, 18 Jan 1999] by simply inheriting from the library
> classes.
No. Sorry, but I don't want to be forced to use classes. I want to
be able to use Ocaml as a "better ML" only. This also applies to
Markus' proposal about the standard library.
> - adding start conditions a la flex to ocamllex
I haven't thought of this really hard, but I bet there is already a
way to do that. If there isn't, I would think hard again to find a
cleaner, more functional (less stateful) way to do it. If the current
condition is kept in a global as in flex, that just drops again the
reentrancy that Christian has been working so hard to achieve.
> - adding a tool for generating perfect hash functions for keyword
> recognition a la gperf; It would be great, if the hash function
> generator could read the set of keywords from annotations in the
> .mly file. I have a rather primitive version, which could be used as
> a starting point.
Yes, I like this one.
--
Ian T Zimmerman <itz@transbay.net>
I came to the conclusion that what was wrong about the guillotine
was that the condemned man had no chance at all, absolutely none.
Albert Camus, _The Outsider_
next prev parent reply other threads:[~1999-01-27 18:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-25 20:53 Hendrik Tews
1999-01-26 19:20 ` Ian T Zimmerman [this message]
1999-01-28 1:30 ` John Prevost
1999-01-28 20:10 ` Hendrik Tews
1999-01-27 1:29 ` Jacques GARRIGUE
1999-01-27 8:27 ` Jean-Christophe Filliatre
1999-01-28 9:34 ` Cuihtlauac ALVARADO
-- strict thread matches above, loose matches on Subject: below --
1999-01-29 0:45 Frank A. Christoph
1999-01-28 13:32 Don Syme
1999-01-29 0:25 ` Markus Mottl
1999-01-31 18:43 ` John Whitley
1999-01-24 21:06 Miles Egan
1999-01-24 23:01 ` Lyn A Headley
1999-01-25 8:44 ` Jean-Christophe Filliatre
1999-01-25 20:45 ` Markus Mottl
1999-01-25 13:36 ` mattwb
1999-01-25 20:48 ` Trevor Jim
1999-01-25 21:57 ` Gerd Stolpmann
1999-01-25 12:45 ` Michel Schinz
1999-01-25 20:37 ` Markus Mottl
1999-01-28 9:54 ` Michel Schinz
1999-01-28 14:13 ` Markus Mottl
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=199901261920.LAA23249@kronstadt.transbay.net \
--to=itz@transbay.net \
--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