From: "David MENTRÉ" <dmentre@linux-france.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] segfault in simple program with 4.02 native
Date: Sat, 06 Sep 2014 22:31:53 +0200 [thread overview]
Message-ID: <540B6F39.20608@linux-france.org> (raw)
In-Reply-To: <540B5B9A.9040207@ens-lyon.org>
Hello Martin,
[ Disclaimer: I know nothing about atdgen. ]
2014-09-06 21:08, Martin Jambon:
> I must say there's a strange feeling about creating more type
> definitions while breaking the type system.
Apparently, such tricks are used for speed reasons. Why not provide two
ways to generate code: one safe using only regular OCaml and one using
Obj tricks. That way, your users could check in case they have an issue
and fall-back to safer code until a proper fix is found.
Nonetheless, I still do think that having correct code is more important
that having fast one, whatever is the speed ratio between the two.
Best regards,
david
next prev parent reply other threads:[~2014-09-06 20:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 21:33 Ashish Agarwal
2014-09-05 21:50 ` Andy Ray
2014-09-05 21:56 ` Richard W.M. Jones
2014-09-05 22:01 ` Sebastien Mondet
2014-09-05 22:06 ` Ashish Agarwal
2014-09-05 22:13 ` Richard W.M. Jones
2014-09-05 22:18 ` Richard W.M. Jones
2014-09-05 22:36 ` Török Edwin
2014-09-05 22:39 ` Martin Jambon
2014-09-05 23:39 ` Ashish Agarwal
2014-09-05 23:59 ` Martin Jambon
2014-09-06 0:12 ` Jeremy Yallop
2014-09-06 5:51 ` Martin Jambon
2014-09-06 6:00 ` Milan Stanojević
2014-09-06 7:46 ` Frédéric Bour
2014-09-06 19:15 ` Martin Jambon
2014-09-06 19:08 ` Martin Jambon
2014-09-06 20:31 ` David MENTRÉ [this message]
2014-09-06 21:57 ` Martin Jambon
2014-09-07 7:34 ` David MENTRÉ
2014-09-07 18:47 ` Alain Frisch
2014-09-08 1:28 ` Martin Jambon
2014-09-13 10:26 ` Martin Jambon
2014-09-14 7:41 ` Martin Jambon
2014-09-05 22:18 ` Christoph Höger
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=540B6F39.20608@linux-france.org \
--to=dmentre@linux-france.org \
--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).