From: "Daniel M. Albro" <albro@humnet.ucla.edu>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Loop times
Date: Mon, 17 Mar 2003 14:01:21 -0800 [thread overview]
Message-ID: <3E7645B1.2040306@humnet.ucla.edu> (raw)
In-Reply-To: <20030317214841.GA467@first.in-berlin.de>
Sorry, I just meant that the version that puts the
exception into a variable outside of the loop is a win over
the one that creates the exception inside the loop. The
fastest loop routine overall was the tail recursive loop,
i.e. the functional/recursive. However, this latest
imperative version has timing that's very close -- the
imperative version that pre-builds the exception takes
just over 28 seconds, and the tail-recursive version
takes just under 27 seconds.
- Dan
Oliver Bandel wrote:
> On Mon, Mar 17, 2003 at 10:59:27AM -0800, Daniel M. Albro wrote:
> [...]
>
>>so it is definitely a win.
>
>
> What is a win?
>
> So much different versions, spread over several mails...
>
> Is functional/recursive a win over imperative?
> Or vice versa? Or what?
>
> Ciao,
> Oliver
>
-------------------
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:[~2003-03-18 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 21:53 Daniel M. Albro
2003-03-17 11:39 ` Fabrice Le Fessant
2003-03-17 18:59 ` Daniel M. Albro
[not found] ` <20030317214841.GA467@first.in-berlin.de>
2003-03-17 22:01 ` Daniel M. Albro [this message]
2003-03-18 9:57 ` Oliver Bandel
2003-03-18 8:52 Oliver Bandel
2003-03-18 15:21 ` Florian Hars
2003-03-18 15:40 ` Noel Welsh
2003-03-19 6:48 ` Daniel M. Albro
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=3E7645B1.2040306@humnet.ucla.edu \
--to=albro@humnet.ucla.edu \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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).