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

On Thu, 6 May 2004, Julien Signoles wrote:
> > 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).

JCF said he manually defunctorized. I'd prefer not to have to butcher my code
to achieve performance, and I'd rather have the compiler do it, if it can.
If ocamldefun can do the work, then I'd rather that there is a compiler switch
to call it transparently rather than have to add more gunk to my makefiles.
Of course, if ocamldefun can do it, modifying one of the existing build
systems to add a defunctorization pass is also an option.

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

So, are you planning to evolve ocamldefun into a whole program optimizing
OCaml compiler? :-)

-- Brian

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


  reply	other threads:[~2004-05-06 16:35 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
2004-05-06 16:35               ` brogoff [this message]
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.58.0405060922470.14721@shell2.speakeasy.net \
    --to=brogoff@speakeasy.net \
    --cc=Julien.Signoles@lri.fr \
    --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).