From: skaller <skaller@users.sourceforge.net>
To: Nicolas Cannasse <ncannasse@motion-twin.com>
Cc: Christophe Raffalli <raffalli@univ-savoie.fr>,
Brian Hurt <bhurt@spnz.org>,
caml-list@inria.fr
Subject: Re: [Caml-list] Obj or not Obj
Date: Mon, 28 Nov 2005 20:33:21 +1100 [thread overview]
Message-ID: <1133170401.4593.138.camel@rosella> (raw)
In-Reply-To: <438AC2AE.3040200@motion-twin.com>
On Mon, 2005-11-28 at 09:41 +0100, Nicolas Cannasse wrote:
> But using the stack is getting speed against correctness, since it will
> overflow for big lists.
But that is an artefact of Unix implementations
designed for flat C code, rather than FPLs. In theory
both stack and heap are bounded only by the smaller of
artificial (that is, deliberately imposed) limits and
total address space.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2005-11-28 9:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 23:53 Efficency of varient types Michael D. Adams
2005-11-26 0:31 ` [Caml-list] " Nicolas Cannasse
2005-11-26 1:22 ` Brian Hurt
2005-11-26 9:39 ` Nicolas Cannasse
2005-11-28 0:17 ` Obj or not Obj Christophe Raffalli
2005-11-28 8:41 ` [Caml-list] " Nicolas Cannasse
2005-11-28 9:27 ` Christophe Raffalli
2005-11-28 9:33 ` skaller [this message]
2005-11-28 8:43 ` Alain Frisch
2005-11-26 2:54 ` [Caml-list] Efficency of varient types skaller
2005-11-27 5:06 ` Michael D. Adams
2005-11-27 5:45 ` Brian Hurt
2005-11-27 10:02 ` Nicolas Cannasse
2005-11-27 15:35 ` Michael D. Adams
2005-11-27 18:08 ` Brian Hurt
2005-12-02 15:07 ` Michael D. Adams
2005-11-26 1:18 ` Jon Harrop
2005-11-27 14:57 ` Lukasz Stafiniak
2005-11-27 15:47 ` Lukasz Stafiniak
2005-11-28 8:14 ` Christophe Raffalli
2005-11-28 7:24 ` David Baelde
2005-11-28 7:49 ` Jacques Garrigue
2005-11-28 10:01 ` Jon Harrop
2005-11-28 10:26 ` Luc Maranget
2005-11-28 7:53 ` Ville-Pertti Keinonen
2005-12-01 17:05 ` Stefan Monnier
2005-12-02 15:07 ` [Caml-list] " Michael D. Adams
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=1133170401.4593.138.camel@rosella \
--to=skaller@users.sourceforge.net \
--cc=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=ncannasse@motion-twin.com \
--cc=raffalli@univ-savoie.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;
as well as URLs for NNTP newsgroup(s).