From: Hendrik Tews <tews@cs.ru.nl>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Camlp4: example/parse_files.ml
Date: Mon, 07 Apr 2008 09:31:09 +0200 [thread overview]
Message-ID: <wwu7ifaazpe.fsf@tandem.cs.ru.nl> (raw)
In-Reply-To: <1207389369-sup-3263@ausone.local> (Nicolas Pouillard's message of "Sat, 05 Apr 2008 12:00:23 +0200")
"Nicolas Pouillard" <nicolas.pouillard@gmail.com> writes:
That's some corner case where first-class modules would help a
lot, however one can use some black magic under the hood to
get the same effect. One need to store extensions once and for
all, in a map from names to "modules".
Sure, if you can store modules in an association list, you are
done. But how to store modules in an association list?
Bye,
Hendrik
next prev parent reply other threads:[~2008-04-07 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 23:13 Hendrik Tews
2008-04-03 15:32 ` [Caml-list] " Nicolas Pouillard
2008-04-03 21:24 ` Hendrik Tews
2008-04-04 13:40 ` Nicolas Pouillard
2008-04-04 14:01 ` Hendrik Tews
2008-04-04 14:19 ` Nicolas Pouillard
2008-04-04 21:30 ` Hendrik Tews
2008-04-05 10:00 ` Nicolas Pouillard
2008-04-07 7:31 ` Hendrik Tews [this message]
2008-04-07 8:10 ` Nicolas Pouillard
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=wwu7ifaazpe.fsf@tandem.cs.ru.nl \
--to=tews@cs.ru.nl \
--cc=caml-list@yquem.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).