Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Quôc Peyrot" <chojin@lrde.epita.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlyacc: named attributes
Date: Sun, 14 Jan 2007 01:29:19 -0800	[thread overview]
Message-ID: <F1A530B7-D9F2-4A08-8D71-C8369ED12B50@lrde.epita.fr> (raw)
In-Reply-To: <1168758441.26042.45.camel@rosella.wigram>


On Jan 13, 2007, at 11:07 PM, skaller wrote:

> On Sun, 2007-01-14 at 01:40 +0100, Till Varoquaux wrote:
>> Hmm,
>> Probably a dumb question, but: why not use Menhir? It's supposedly
>> strictly more powerfull than ocamlyacc and has this feature.
>
> Two reasons. The first is political: Menhir isn't part of the
> standard Ocaml distribution. This means clients of my system
> will have to download and install and additional package
> before they can build mine. That includes on Windows.
> If a binary wasn't available they'd have to build from source.
>
> This may not be a big deal if it is pure Ocaml, which from
> memory it is, right? However then I have to include the sources
> in my own package, which introduces a repository synchronisation
> problem .. and unless Menhir has a liberal licence .. also a
> licencing problem.
>
> In addition there is a reliability and responsibility issue:
> the Ocaml team is paid to maintain Ocaml.

Menhir is developed by two members of the Inria's Rocquencourt site:
Francois Pottier and Yann Régis-Gianas.

Thus, although they are not paid to maintain Menhir (or maybe they  
are?),
it sounds close enough to me...

-- 
Regards,
Quôc


      reply	other threads:[~2007-01-14  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 22:59 skaller
2007-01-14  0:40 ` [Caml-list] " Till Varoquaux
2007-01-14  7:07   ` skaller
2007-01-14  9:29     ` Quôc Peyrot [this message]

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=F1A530B7-D9F2-4A08-8D71-C8369ED12B50@lrde.epita.fr \
    --to=chojin@lrde.epita.fr \
    --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