From: "Mattias Waldau" <mattias.waldau@abc.se>
To: "'Christophe Raffalli'" <Christophe.Raffalli@univ-savoie.fr>,
<brogoff@speakeasy.net>
Cc: "'Andrew Kennedy'" <akenn@microsoft.com>,
"'Brian Hurt'" <brian.hurt@qlogic.com>,
"'Ocaml Mailing List'" <caml-list@inria.fr>
Subject: RE: [Caml-list] @, List.append, and tail recursion
Date: Fri, 31 Jan 2003 11:33:44 +0100 [thread overview]
Message-ID: <01c401c2c914$3b3bf830$0a00a8c0@gateway> (raw)
In-Reply-To: <3E38F6F6.7000206@univ-savoie.fr>
> brogoff@speakeasy.net wrote:
> > Thanks for the reference. I get nailed by this a couple of times a
> > year, and I usually just blame myself for being sloppy and recode
> > all of my maps, appends, and filters to remove it. I think it would
I agree that this is recurring problem, I myself often get bit by
List.map.
It makes it very easy to make non-scalable program, works for input less
that 1000 elements, and the when applied to a large problem it fails
without a trace. It is very difficult to find the location of the
problem if you use the native compiler, and most of these programs
doesn't even work using the byte-code compiler.
So one of my coding guidelines is:
- do not use List.map
I would like a prefer other solutions.
/mattias
-------------------
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-01-31 10:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 15:35 Andrew Kennedy
2003-01-30 1:44 ` brogoff
2003-01-30 9:57 ` Christophe Raffalli
2003-01-30 16:03 ` Brian Hurt
2003-01-31 10:33 ` Mattias Waldau [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-31 22:27 Harrison, John R
2003-01-31 19:58 Harrison, John R
2003-01-31 21:04 ` Brian Hurt
2003-01-31 17:32 Diego Olivier Fernandez Pons
2003-01-24 0:48 Brian Hurt
2003-01-30 18:10 ` Olivier Andrieu
2003-01-30 19:46 ` Brian Hurt
2003-01-30 20:52 ` Olivier Andrieu
2003-01-30 21:57 ` Brian Hurt
2003-01-31 2:16 ` james woodyatt
2003-01-31 17:05 ` Diego Olivier Fernandez Pons
2003-01-31 19:52 ` Brian Hurt
2003-01-31 21:34 ` Issac Trotts
2003-01-31 17:13 ` Brian Hurt
2003-01-31 17:42 ` brogoff
2003-01-31 19:18 ` Russ Ross
2003-01-31 19:32 ` Alexander V. Voinov
2003-02-01 2:30 ` brogoff
2003-01-31 23:12 ` Issac Trotts
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='01c401c2c914$3b3bf830$0a00a8c0@gateway' \
--to=mattias.waldau@abc.se \
--cc=Christophe.Raffalli@univ-savoie.fr \
--cc=akenn@microsoft.com \
--cc=brian.hurt@qlogic.com \
--cc=brogoff@speakeasy.net \
--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