From: Brian Naylor <bwv211mail@yahoo.com>
To: caml-list@inria.fr
Subject: [Caml-list] functor question
Date: Tue, 23 Jul 2002 21:26:35 -0700 (PDT) [thread overview]
Message-ID: <20020724042635.18417.qmail@web13404.mail.yahoo.com> (raw)
Is there any efficiency difference between:
module Foo = Make (Bar) (Baz)
and
module Both = struct module Bar = Bar module Baz = Baz end
module Foo = Make (Both)
In other words, is it better to coalesce structures into a single functor
application rather than to apply multiple functors? Do I pay more indirection
costs in the first case? Thanks.
__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2002-07-24 4:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 4:26 Brian Naylor [this message]
2002-07-25 9:21 ` Xavier Leroy
2002-07-25 9:55 ` [Caml-list] Functors, Modules and Indirections Thorsten Ohl
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=20020724042635.18417.qmail@web13404.mail.yahoo.com \
--to=bwv211mail@yahoo.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).