From: skaller <skaller@users.sourceforge.net>
To: Alain Frisch <Alain.Frisch@inria.fr>
Cc: "Martin Jambon" <martin1977@laposte.net>,
"Eric Breck" <ebreck@cs.cornell.edu>,
"Bünzli Daniel" <daniel.buenzli@epfl.ch>,
caml-list@inria.fr
Subject: Re: Camlp4 mysteries (was Re: On language extensions (was Re: [Caml-list] global record))
Date: Fri, 21 Jul 2006 10:29:48 +1000 [thread overview]
Message-ID: <1153441788.20265.35.camel@rosella.wigram> (raw)
In-Reply-To: <44C013EC.2080201@inria.fr>
On Fri, 2006-07-21 at 01:38 +0200, Alain Frisch wrote:
> Martin Jambon wrote:
> > Otherwise it's possible to define well-disciplined syntax extensions.
> > For example, if each new syntax construct (new rule) is forced to start
> > with a unique, registered keyword and end with "end", then different
> > syntax extensions that follow this rule should play well together.
>
> Except that any new keyword can potentially break existing code. You'd
> need some other syntactical convention.
If you follow the rules I specified, this is not possible.
My rule is: extensions must be enabled in every file that
use them:
#syntax extension_name
Then the extension only affects files deliberately written
using the extension, so there won't be any code breakage
unless the extension itself is upgraded, or, ocaml itself
is upgraded.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2006-07-21 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 1:12 On language extensions (was Re: [Caml-list] global record) Eric Breck
2006-07-20 5:16 ` skaller
2006-07-20 6:29 ` Stefano Zacchiroli
2006-07-20 8:57 ` Jean-Marie Gaillourdet
2006-07-20 12:42 ` Bünzli Daniel
2006-07-20 12:40 ` Camlp4 mysteries (was Re: On language extensions (was Re: [Caml-list] global record)) Martin Jambon
2006-07-20 23:38 ` Alain Frisch
2006-07-21 0:11 ` Martin Jambon
2006-07-21 0:29 ` skaller [this message]
2006-07-21 0:31 ` Martin Jambon
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=1153441788.20265.35.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=Alain.Frisch@inria.fr \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@epfl.ch \
--cc=ebreck@cs.cornell.edu \
--cc=martin1977@laposte.net \
/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).