From: "Oliver Bandel" <oliver@first.in-berlin.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Scilab: Why not written in OCaml?
Date: Sat, 19 Sep 2009 23:02:17 +0200 [thread overview]
Message-ID: <20090919230217.401810j08edzs6hl@webmail.in-berlin.de> (raw)
In-Reply-To: <4d1b2df20909191003h357f3b8fr97dee44022c81034@mail.gmail.com>
Hi,
Zitat von "Philippe Wang" <philippe.wang.lists@gmail.com>:
> Why not use Bigloo? It's a efficient scheme compiler, also developed
> at INRIA.
> http://www-sop.inria.fr/mimosa/fp/Bigloo/
[...]
I looked at bigloo before I came to OCaml.
I decided against it.
Not only because of schem's ((((())))()(()()))))))-terror ;-)
but also (main reason) because of this:
"Bigloo produces C files. C code uses the C stack,
so some programs can?t be properly tail recursive.
Nevertheless all simple tail recursions are compiled
without stack consumption."
This was not really inspiring confidence.
Even if I did not really know much about that topic tailrec-topic,
it seemed to be a basic feature, and other scheme implementations did
not have such a limitation...
...then I had contact to Haskell and Ocaml and decided OCaml to be my
favourite.
I never looked at bigloo again, but that quote above is from the
bigloo-documentation that I just now downloaded to assure the point
has not changed during the last years.
>
> Just kidding,
[...]
oh, I saw this too late;-)
Ciao,
Oliver
next prev parent reply other threads:[~2009-09-19 21:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 22:59 Oliver Bandel
2009-09-19 7:39 ` [Caml-list] " Stéphane Lescuyer
2009-09-19 15:23 ` Jon Harrop
2009-09-19 17:03 ` Philippe Wang
2009-09-19 21:02 ` Oliver Bandel [this message]
2009-09-19 21:04 ` Oliver Bandel
2009-09-19 21:30 ` Adrien
2009-09-19 10:16 ` Erik de Castro Lopo
2009-09-20 9:08 ` rixed
2009-09-20 11:32 ` Jon Harrop
2009-09-20 17:25 ` Stefan Monnier
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=20090919230217.401810j08edzs6hl@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@yquem.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