From: Diego Olivier FERNANDEZ PONS <diego.fernandez_pons@etu.upmc.fr>
To: skaller <skaller@users.sourceforge.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Bug in ocamlyacc
Date: Tue, 24 Apr 2007 12:23:38 +0200 [thread overview]
Message-ID: <20070424122338.ozkvhzfhckcskkc4@webmail.etu.upmc.fr> (raw)
In-Reply-To: <1177392571.10100.46.camel@rosella.wigram>
Bonjour,
> I won't use Menhir for that reason either.[...]
Come on, Skaller. You know as well as everyone that adding a tool that
is not mature enough to the standard distribution is a bad idea.
Mehnir is clearly the "official" candidate for replacement of
CamlYacc, without yet being mandatory. This gives you the time to
port, criticize and ask for improvements. Look the mess that happened
with CamlP4 which didn't follow this pattern.
So instead of being complaining because Mehnir is not yet in the
standard distribution, you should be porting your CamlYacc code to
ensure that when the tools are swapped, Menhir will make your code
simpler, faster and cleaner.
Diego Olivier
next prev parent reply other threads:[~2007-04-24 10:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 22:03 David Allsopp
2007-04-24 5:29 ` [Caml-list] " skaller
2007-04-24 10:23 ` Diego Olivier FERNANDEZ PONS [this message]
2007-04-24 12:06 ` ls-ocaml-developer-2006
2007-04-24 18:25 ` skaller
2007-04-24 20:17 ` new+old Camlp4 (was Re: [Caml-list] Bug in ocamlyacc) Martin Jambon
2007-04-24 21:38 ` Yaron Minsky
2007-04-24 22:53 ` new+old Camlp4 ls-ocaml-developer-2006
2007-04-25 1:03 ` new+old Camlp4 (was Re: [Caml-list] Bug in ocamlyacc) skaller
2007-04-25 2:29 ` Daniel de Rauglaudre
2007-04-25 17:11 ` Markus Mottl
2007-04-26 3:00 ` skaller
2007-04-27 9:15 ` new+old Camlp4 Xavier Leroy
2007-04-27 13:43 ` Markus Mottl
2007-05-02 8:03 ` [Caml-list] " Hendrik Tews
2007-04-24 14:32 ` [Caml-list] Bug in ocamlyacc Francois Pottier
2007-04-24 18:59 ` skaller
2007-04-24 19:59 ` Francois Pottier
2007-04-27 15:56 ` brogoff
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=20070424122338.ozkvhzfhckcskkc4@webmail.etu.upmc.fr \
--to=diego.fernandez_pons@etu.upmc.fr \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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