caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@uga.edu>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] camlp4 vs. ocamllex/yacc?
Date: 25 Jan 2003 21:50:47 -0500	[thread overview]
Message-ID: <87ptqkpqt4.fsf@cs.uga.edu> (raw)
In-Reply-To: <15921.22474.602526.543452@lri.lri.fr>

Jean-Christophe Filliatre <Jean-Christophe.Filliatre@lri.fr> writes:

...
> The (sole?)  advantage of ocamlyacc is when you already have a YACC
> grammar. Turning it into an ocamlyacc grammar is almost immediate.

I am using ocamlyacc for a compilers course.  I think I'm sticking to
ocamlyacc because all the other students are using bison, but I got
curious when reading this thread.  I decided to check out camlp4, and
I found this page:

  http://caml.inria.fr/camlp4/

... where I read what could be construed as another disadvantage of
camlp4:

  Developpment stopped: no more extension, or bug fix is assured

I'm not sure what to make of it, though.  There's an old thread in the
archives where the principle camlp4 developer at the time seems to
indicate an intention to only work on a version that's separate from
the ocaml distribution.

What's the current situation?  Is there some kind of version split
going on now?  

-- 
--Ed L Cashin            |   PGP public key:
  ecashin@uga.edu        |   http://noserose.net/e/pgp/
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      parent reply	other threads:[~2003-01-27  6:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 14:15 Daniel Andor
2003-01-24 14:32 ` Jacques Carette
2003-01-24 15:12 ` Jean-Christophe Filliatre
2003-01-24 16:21   ` Alain.Frisch
2003-01-26  2:50   ` Ed L Cashin [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=87ptqkpqt4.fsf@cs.uga.edu \
    --to=ecashin@uga.edu \
    --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;
as well as URLs for NNTP newsgroup(s).