From: Martin Chabr <martin_chabr@yahoo.de>
To: Pal-Kristian Engstad <pal_engstad@naughtydog.com>
Cc: caml-list@yquem.inria.fr
Subject: Ant: Re: Ant: Re: [Caml-list] Avoiding shared data
Date: Sat, 1 Oct 2005 23:05:19 +0200 (CEST) [thread overview]
Message-ID: <20051001210520.64728.qmail@web26809.mail.ukl.yahoo.com> (raw)
In-Reply-To: <200509301707.01281.pal_engstad@naughtydog.com>
Hello Pal-Kristian,
I agree with you that functional code written in a
tail recursive style is hard to read. Sometimes you
have to do it that way if you want to avoid a stack
overflow.
I hope that one day functional language compilers will
do that optimization for you - convert a
non-tail-recursive code into a tail-recursive one. Do
you know of some progress in that direction?
Regards,
Martin
--- Pal-Kristian Engstad <pal_engstad@naughtydog.com>
wrote:
> I've always thought that this was a really bad
> argument from the ML camp. The
> logic of complicated control-paths is very easily
> made a zillion times worse
> by writing in a tail-recursive style. It is *not* a
> good programming practice
> to make hard-to-read code!
___________________________________________________________
Was denken Sie über E-Mail? Wir hören auf Ihre Meinung: http://surveylink.yahoo.com/wix/p0379378.aspx
next prev parent reply other threads:[~2005-10-01 21:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 21:32 Martin Chabr
2005-09-26 0:23 ` [Caml-list] " Bill Wood
2005-09-26 7:57 ` Claudio Sacerdoti Coen
2005-09-26 8:17 ` William Lovas
2005-09-26 21:07 ` Ant: " Martin Chabr
2005-09-26 22:08 ` Jon Harrop
2005-09-30 22:57 ` Oliver Bandel
2005-10-01 0:07 ` Pal-Kristian Engstad
2005-10-01 5:46 ` Bill Wood
2005-10-01 8:27 ` Wolfgang Lux
2005-10-01 18:02 ` Wolfgang Lux
2005-10-01 21:50 ` Ant: " Martin Chabr
2005-10-01 12:34 ` Oliver Bandel
2005-10-01 13:58 ` Bill Wood
2005-10-01 21:05 ` Martin Chabr [this message]
2005-10-03 0:41 ` Ant: " skaller
2005-10-03 1:13 ` Seth J. Fogarty
2005-10-03 13:09 ` Thomas Fischbacher
2005-10-03 14:57 ` skaller
2005-10-03 20:03 ` Ant: " Martin Chabr
2005-10-03 20:25 ` Thomas Fischbacher
2005-10-03 21:08 ` Jon Harrop
2005-10-04 18:06 ` Ant: " Martin Chabr
2005-10-04 18:32 ` Jon Harrop
2005-10-04 2:53 ` skaller
2005-10-04 16:15 ` Brian Hurt
2005-10-04 16:47 ` FP/IP and performance (in general) and Patterns... (Re: [Caml-list] Avoiding shared data) Oliver Bandel
2005-10-04 22:38 ` Michael Wohlwend
2005-10-05 0:31 ` Jon Harrop
2005-10-04 22:39 ` Christopher A. Watford
2005-10-04 23:14 ` Jon Harrop
2005-10-05 12:10 ` Oliver Bandel
2005-10-05 13:08 ` Jon Harrop
2005-10-05 15:28 ` skaller
2005-10-05 20:52 ` Ant: " Martin Chabr
2005-10-05 23:21 ` Markus Mottl
2005-10-06 16:54 ` brogoff
2005-10-05 0:45 ` Brian Hurt
2005-10-04 18:09 ` Ant: Re: Ant: Re: Ant: Re: Ant: Re: [Caml-list] Avoiding shared data Martin Chabr
2005-10-05 8:42 ` skaller
2005-10-05 11:14 ` Andrej Bauer
2005-10-01 21:36 ` Ant: Re: Ant: " Martin Chabr
2005-10-03 11:51 ` getting used to FP-programming (Re: Ant: Re: Ant: Re: [Caml-list] Avoiding shared data) Oliver Bandel
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=20051001210520.64728.qmail@web26809.mail.ukl.yahoo.com \
--to=martin_chabr@yahoo.de \
--cc=caml-list@yquem.inria.fr \
--cc=pal_engstad@naughtydog.com \
/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