From: William Chesters <williamc@paneris.org>
To: caml-list@inria.fr
Subject: Re: status of some big "important" features?
Date: Tue, 2 Jan 2001 18:39:55 +0100 (CET) [thread overview]
Message-ID: <14930.4452.271488.519939@beertje.william.bogus> (raw)
In-Reply-To: <20001231040811.G2272@verdot.inria.fr>
Daniel de Rauglaudre writes:
> Camlp4 allows to make syntax extensions. We could imagine something to
> make typing extensions and code generating extensions. But I don't
> know how to do that, and even if it is possible in a simple way.
>
> Do other caml-list readers have an opinion about that?
The actual source code for the compiler as it is now is pretty decent,
remarkably so given its maturity, and it's hard to imagine any useful
"semantic extension" mechanism being much simpler than just hacking the
relevant bits of camlc.
My 2p,
W
next prev parent reply other threads:[~2001-01-03 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-26 23:47 Chris Hecker
2000-12-28 9:10 ` Daniel de Rauglaudre
2000-12-30 19:30 ` Chris Hecker
2000-12-30 20:53 ` Daniel de Rauglaudre
2000-12-31 1:58 ` Chris Hecker
2000-12-31 3:08 ` Daniel de Rauglaudre
2001-01-02 17:39 ` William Chesters [this message]
2000-12-31 20:39 ` John Max Skaller
2000-12-28 20:19 ` A proposal for overloading Christophe Raffalli
2001-01-02 10:38 ` Didier Remy
2001-01-02 19:08 ` Christophe Raffalli
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=14930.4452.271488.519939@beertje.william.bogus \
--to=williamc@paneris.org \
--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).