From: "Dave Berry" <Dave@kal.com>
To: <caml-list@inria.fr>
Subject: [Caml-list] Camlp4 "vs" JSE
Date: Wed, 6 Feb 2002 13:37:00 -0000 [thread overview]
Message-ID: <8E31D6933A2FE64F8AE3CC1381EEDCE7232D99@NT.kal.com> (raw)
Two ex-colleagues of mine published a paper in last year's OOPSLA about
a macro system for Java. In their paper they briefly mention Camlp4 in
the "related work" section. They say that because Camlp4 is
grammar-based, it can't guarantee parseability. Is this true, or did
they not understand Camlp4 properly?
Does anyone here have any more to contribute comparing the two
approaches?
The authors in question are Jonathan Bachrach and Keith Playford, and
the title of their paper is something like "The Java Syntactic
Extender", OOPSLA 2001.
Dave.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2002-02-06 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 13:37 Dave Berry [this message]
2002-02-06 14:59 ` Daniel de Rauglaudre
2002-02-06 22:14 ` Chris Hecker
2002-02-07 5:25 ` Daniel de Rauglaudre
2002-02-07 14:08 Krishnaswami, Neel
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=8E31D6933A2FE64F8AE3CC1381EEDCE7232D99@NT.kal.com \
--to=dave@kal.com \
--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).