From: Berke Durak <berke@altern.org>
To: caml-list@inria.fr
Subject: [Caml-list] Module (re)construction cost
Date: Sun, 22 Jul 2001 10:18:45 +0200 [thread overview]
Message-ID: <20010722101845.A31393@localhost.localdomain> (raw)
Does building a functorized module cost anything at all ? I have a
program with a lot of high-level modules that depend on a small set of
interdependent modules parametrized by one common module. Should the
high-level modules get the (already-built) core modules as
``parameters'' from the main module, or should they reconstruct them
by getting only the common module from their parent ? i.e. does functor
application cost anything (time ? memory ?).
--
Berke
-------------------
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:[~2001-07-22 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 8:18 Berke Durak [this message]
2001-07-27 13:25 ` Xavier Leroy
2001-07-27 14:09 ` Markus Mottl
2001-07-27 17:51 ` William Chesters
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=20010722101845.A31393@localhost.localdomain \
--to=berke@altern.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