From: "Török Edwin" <edwin+ml-ocaml@etorok.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Haskell vs OCaml
Date: Thu, 21 Mar 2013 23:55:23 +0200 [thread overview]
Message-ID: <514B81CB.3070103@etorok.net> (raw)
In-Reply-To: <06b901ce25ca$cc415be0$64c413a0$@ffconsultancy.com>
On 03/21/2013 02:26 AM, Jon Harrop wrote:
> Presenta is obviously a counter-example for reliability. 100% OCaml code
> isn't supposed to be able to segfault...
Were you able to track down the cause?
I'm aware of at least one problem before OCaml 4.00.0 (segfault instead of stack overflow,
possible even with pure OCaml code, because even that would eventually call the C functions in the stdlib), but I'm sure there
can be other reasons.
On a related note perhaps it would be useful to have a tool that checks whether OCaml code (and its dependencies!) uses "unsafe" features,
or lacks tail calls, etc.
Best regards,
--Edwin
next prev parent reply other threads:[~2013-03-21 21:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.e3jKyg6bl9+vTkPgypQ4ZRzEoos@ifi.uio.no>
2013-03-18 9:08 ` [Caml-list] " adrian.alexander.may
2013-03-18 9:48 ` Malcolm Matalka
2013-03-18 9:59 ` Gabriel Scherer
2013-03-18 11:05 ` Adrian May
2013-03-18 11:26 ` Kakadu
2013-03-18 18:05 ` [Caml-list] " Chet Murthy
2013-03-20 20:44 ` Jon Harrop
2013-03-20 21:10 ` Yaron Minsky
2013-03-21 0:26 ` Jon Harrop
2013-03-21 20:58 ` Yaron Minsky
2013-03-23 23:33 ` Richard W.M. Jones
2013-03-21 21:55 ` Török Edwin [this message]
2013-03-22 17:51 ` Jon Harrop
2013-03-22 18:46 ` Daniel Bünzli
2013-03-22 19:53 ` Jon Harrop
2013-03-22 20:23 ` Daniel Bünzli
2013-03-22 22:13 ` Jon Harrop
2013-03-22 23:35 ` Daniel Bünzli
2013-03-22 23:47 ` Chet Murthy
2013-03-23 0:02 ` Daniel Bünzli
2013-03-23 0:09 ` Chet Murthy
2013-03-23 1:17 ` Jon Harrop
2013-03-23 1:41 ` oliver
2013-03-23 1:15 ` Jon Harrop
2013-03-23 1:50 ` Daniel Bünzli
2013-03-25 1:22 ` Francois Berenger
2013-03-23 1:25 ` oliver
2013-03-19 1:23 ` [Caml-list] " Francois Berenger
2013-03-26 10:36 ` Nicolas Braud-Santoni
2013-03-26 0:49 ` Kristopher Micinski
2013-03-26 2:37 ` Erik de Castro Lopo
2013-03-26 2:57 ` Kristopher Micinski
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=514B81CB.3070103@etorok.net \
--to=edwin+ml-ocaml@etorok.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;
as well as URLs for NNTP newsgroup(s).