caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Julien Signoles <Julien.Signoles@lri.fr>
To: brogoff@speakeasy.net
Cc: Julien Signoles <Julien.Signoles@lri.fr>,
	Jon Harrop <jdh30@cam.ac.uk>, <caml-list@inria.fr>
Subject: Re: [Caml-list] Functors
Date: Thu, 6 May 2004 14:26:26 +0200 (MEST)	[thread overview]
Message-ID: <Pine.LNX.4.43.0405061418200.14392-100000@pc8-119.lri.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0405051257110.15595@grace.speakeasy.net>


> In any case, the absence of a defunctorization step means that we often
> have a choice between performance and a functorized programming style, which
> stinks.

I don't think you have a stinking choice. My opinion is: always choose a
functorized programming style and, if this style significantly reduces
performance, then use a defunctorizer like ocamldefun. For example, see
the Jean-Christophe Filliâtre's contribution to this thread
(http://caml.inria.fr/archives/200405/msg00087.html). First, he
implements an algorithm in a functorized style. Then, he sadly remarks
poor performance due to functors. Finally, he defunctorizes and boosts
the performance.

> Does ocamldefun deal with the recursive modules of 3.07?

The current version (v1.11) of ocamldefun only works with ocaml 3.06 and
so it doesn't deal with recursive modules. A version of ocamldefun dealing
with ocaml 3.07 is on my TODO list.

> MLton began as an SML defunctorizer if I'm not mistaken, but has evolved
> into a whole program optimizing compiler.

You're not mistaken :-). See http://www.mlton.org/history.html.

Cheers,
Julien
-- 
mailto:Julien.Signoles@lri.fr ; http://www.lri.fr/~signoles
"In theory, practice and theory are the same,
but in practice they are different" (Larry McVoy)

-------------------
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


  parent reply	other threads:[~2004-05-06 12:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02  9:12 Jon Harrop
2004-05-02 10:24 ` Martin Jambon
2004-05-02 13:34   ` Jon Harrop
2004-05-02 14:12     ` skaller
2004-05-02 16:49       ` Jon Harrop
2004-05-03  0:20         ` skaller
2004-05-03 14:43           ` Jacques Carette
2004-05-03 16:09             ` Alain.Frisch
2004-05-03 18:53               ` Jacques Carette
2004-05-03 19:17                 ` [Caml-list] Mathematica Jon Harrop
2004-05-03 22:51                 ` [Caml-list] Functors Alain.Frisch
2004-05-03 16:02     ` Julien Signoles
2004-05-03 18:41       ` Jon Harrop
2004-05-04  7:25         ` Jean-Christophe Filliatre
2004-05-05  8:15         ` Julien Signoles
2004-05-05 20:41           ` brogoff
2004-05-06 11:16             ` Jon Harrop
2004-05-06 20:23               ` Alain.Frisch
2004-05-06 18:26                 ` Olivier Grisel
2004-05-06 12:26             ` Julien Signoles [this message]
2004-05-06 16:35               ` brogoff
2004-05-02 17:18   ` David Brown

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=Pine.LNX.4.43.0405061418200.14392-100000@pc8-119.lri.fr \
    --to=julien.signoles@lri.fr \
    --cc=brogoff@speakeasy.net \
    --cc=caml-list@inria.fr \
    --cc=jdh30@cam.ac.uk \
    /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).