From: William Lovas <wlovas@stwing.upenn.edu>
To: caml-list@inria.fr
Subject: Re: fancy types (was Re: [Caml-list] ocaml killer)
Date: Fri, 30 Jan 2004 22:39:16 -0500 [thread overview]
Message-ID: <20040131033915.GA2151@force.stwing.upenn.edu> (raw)
In-Reply-To: <Pine.LNX.4.58.0401301134410.14159@seekar.cip.physik.uni-muenchen.de>
On Fri, Jan 30, 2004 at 11:36:13AM +0100, Thomas Fischbacher wrote:
>
> On Thu, 29 Jan 2004, William Lovas wrote:
>
> > # type ('a, 'b) specialist = S of (('a, 'b) specialist -> 'a -> 'b);;
> > type ('a, 'b) specialist = S of (('a, 'b) specialist -> 'a -> 'b)
> > # let fac n =
> > let do_rec (S specialist) n =
> > if n = 0 then
> > 1
> > else
> > n * specialist (S specialist) n
> > in
> > do_rec (S do_rec) n;;
> > val fac : int -> int = <fun>
>
> Hm, correct me if I am wrong, but to me this looks as if you had to
> unnecessarily cons at every recursive call...
Well, it depends on what you mean by "unnecessarily" and what you mean by
"cons". First, if by "cons" you mean "call a constructor", then yes, i did
have to cons at every recursive call. However, if by "cons" you mean
"allocate memory", i can't say for sure by looking at this code -- it says
nothing about the optimizations applied to variant types during compilation
or potential opportunities for structure sharing. I strongly suspect that
memory need not be allocated, though, in which case the answer is no, i did
not have to allocate memory at every recursive cell.
As far as "unnecessarily" goes, to me the calls are perfectly necessary --
otherwise the code wouldn't make sense -- I think in types first and code
second. :)
So if efficiency is your concern, you've nothing to worry about. If its
verbosity, then you have a fair argument -- you just have to weigh the
development time benefits against the small amount of extra code you have
to write beyond what LISP would require you to write. Personally, i think
it's worth it, but that's just an opinion.
cheers,
William
-------------------
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 prev parent reply other threads:[~2004-01-31 3:39 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 6:32 [Caml-list] ocaml killer Alexander Epifanov
2004-01-27 8:56 ` Alex Baretta
2004-01-27 9:43 ` Alexander Epifanov
2004-01-27 18:32 ` Shawn Wagner
2004-01-28 4:38 ` skaller
2004-01-28 5:30 ` james woodyatt
[not found] ` <40168498.6070708@tfb.com>
2004-01-27 19:10 ` Alex Baretta
2004-01-28 13:29 ` David Fox
2004-01-28 15:12 ` Eray Ozkural
2004-01-27 9:41 ` Alexander Danilov
2004-01-27 9:57 ` Alexander Epifanov
2004-01-27 16:43 ` Eric Stokes
2004-01-27 18:19 ` David Fox
2004-01-27 18:47 ` Richard Jones
2004-01-27 19:29 ` Eric Stokes
2004-01-28 13:30 ` Eray Ozkural
2004-01-28 23:26 ` Chet Murthy
2004-01-28 23:47 ` Martin Berger
2004-01-29 0:00 ` Chet Murthy
2004-01-29 0:04 ` Chet Murthy
2004-01-29 0:11 ` Martin Berger
2004-01-29 0:34 ` Chet Murthy
2004-01-29 0:47 ` [Caml-list] ocaml killer' Matt Gushee
2004-01-29 8:52 ` [Caml-list] ocaml killer Thomas Fischbacher
2004-01-29 16:20 ` fancy types (was Re: [Caml-list] ocaml killer) William Lovas
2004-01-29 17:13 ` james woodyatt
2004-01-29 17:26 ` Benedikt Grundmann
2004-01-29 17:17 ` Thomas Fischbacher
2004-01-29 17:41 ` Andreas Rossberg
2004-01-29 19:18 ` William Lovas
2004-01-30 10:36 ` Thomas Fischbacher
2004-01-31 3:39 ` William Lovas [this message]
2004-02-01 2:11 ` Vasile Rotaru
2004-02-02 11:08 ` Florian Hars
2004-01-29 18:33 ` Alex Baretta
2004-01-29 17:53 ` [Caml-list] ocaml killer skaller
2004-01-29 5:20 ` Brian Hurt
2004-01-29 6:36 ` Alexander Epifanov
2004-01-29 8:53 ` [Caml-list] ocaml and concurrency james woodyatt
2004-01-29 9:46 ` Vitaly Lugovsky
2004-01-29 10:37 ` Martin Berger
2004-01-29 11:51 ` Michael Hicks
2004-01-29 12:20 ` Alex Baretta
2004-01-29 12:43 ` Martin Berger
2004-01-29 15:42 ` Vitaly Lugovsky
2004-01-29 16:11 ` Martin Berger
2004-01-29 16:56 ` Andreas Rossberg
2004-01-29 17:19 ` james woodyatt
2004-01-29 17:43 ` Martin Berger
2004-01-29 17:54 ` Andreas Rossberg
2004-01-29 18:08 ` Martin Berger
2004-01-30 0:19 ` Lauri Alanko
2004-01-29 19:37 ` skaller
2004-01-30 0:05 ` Martin Berger
2004-01-30 6:52 ` Brian Hurt
2004-01-30 8:53 ` Issac Trotts
2004-01-30 20:45 ` skaller
2004-01-31 6:29 ` Brian Hurt
2004-01-30 20:12 ` skaller
2004-01-29 18:35 ` skaller
2004-01-29 9:56 ` Alex Baretta
2004-01-29 18:26 ` skaller
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=20040131033915.GA2151@force.stwing.upenn.edu \
--to=wlovas@stwing.upenn.edu \
--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