From: skaller <skaller@users.sourceforge.net>
To: Diego Olivier FERNANDEZ PONS <diego.fernandez_pons@etu.upmc.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Bug in ocamlyacc
Date: Wed, 25 Apr 2007 04:25:18 +1000 [thread overview]
Message-ID: <1177439118.6172.18.camel@rosella.wigram> (raw)
In-Reply-To: <20070424122338.ozkvhzfhckcskkc4@webmail.etu.upmc.fr>
On Tue, 2007-04-24 at 12:23 +0200, Diego Olivier FERNANDEZ PONS wrote:
> 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.
Not if it is optional, like the ocamlbuild tool for example.
> 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.
There do indeed appear to be some issues with camlp4.
However what was done was the 'right thing' despite that --
IMHO of course.
First: few would have tested it, given the incompatibilities,
it it were not forced onto the market.
Second: Ocaml 3.10 is still in beta, and the author(s) of
camlp4 *needed* the feedback and participation from the community.
Third: the community wanted a better camlp4: this is the price,
and I believe most people using camlp4 are willing to help
and get it working.
Fourth: it had to be done sometime, and I would guess that
there was no technical choice but a painful change.
However with Menhir, the issues aren't so bad because it doesn't
yet need to replace Ocamlyacc, just be available as an alternative.
> So instead of being complaining because Mehnir is not yet in the
> standard distribution,
I'm not complaining, but stating my reasons why I think it
should be
> you should be porting your CamlYacc code to
> ensure that when the tools are swapped, Menhir will make your code
> simpler, faster and cleaner.
.. and also making it clear, I hope, why I won't be
using it in my product until it is.
Unfortunately my team also has limited resources.
I already tried Menhir and provided some feedback.
I'm supportive of it. But I cannot convert my
production code to use a third party library
unless I can include the source in my product.
Felix doesn't use any external third party libraries:
it uses the system Ocaml and C++ libraries, and it
uses Cil/Frontc, Elkhound and Tre .. which are included
in the Felix system as source code and built by the
Felix build system.
I might consider doing that with Menhir if the licence
were FFAU like MIT/BSD/Boost/Creative Commons.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-04-24 18:25 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
2007-04-24 12:06 ` ls-ocaml-developer-2006
2007-04-24 18:25 ` skaller [this message]
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=1177439118.6172.18.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=diego.fernandez_pons@etu.upmc.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