From: "David Allsopp" <dra-news@metastack.com>
To: "OCaml List" <caml-list@yquem.inria.fr>
Subject: Bug in ocamlyacc
Date: Mon, 23 Apr 2007 23:03:30 +0100 [thread overview]
Message-ID: <001401c785f3$3af5e890$6a7ba8c0@treble> (raw)
With regards to the closing comment to Bug Report #4251:
> doligez: We won't spend time fixing minor issues in ocamlyacc because the
> future is in menhir. The workaround is obvious anyway.
Does this mean that menhir will be moved to the O'Caml distribution at some
point? I don't think I'm the only person reading this list who doesn't use
Menhir (at the moment) solely because it is not part of the *standard*
O'Caml distribution. Unless Menhir is due to become the official,
distributed and supported replacement for ocamlyacc, then this comment is
not terribly impressive[1]
David
[1] Though this specific problem is utterly trivial to work around, as
stated!
next reply other threads:[~2007-04-23 22:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 22:03 David Allsopp [this message]
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
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='001401c785f3$3af5e890$6a7ba8c0@treble' \
--to=dra-news@metastack.com \
--cc=caml-list@yquem.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