caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Carr <jfc@mit.edu>
To: caml-list@inria.fr
Subject: [Caml-list] What is the safe subset of OCaml?
Date: Tue, 12 Apr 2011 14:19:47 -0400	[thread overview]
Message-ID: <201104121819.p3CIJlw8019462@outgoing.mit.edu> (raw)


What must be removed from OCaml to get a safe subset of the language?
There is a proof that a smaller language is safe (Rémy 2000).  I don't
know the full difference between that smaller language and the one we
have today.  In the standard library, Obj, Marshal, and everything with
unsafe in the name are unsafe.  External functions are unsafe.  Programs
may overflow the system stack.  Am I missing anything?

My recollection from a previous discussion is that polymorphic
exceptions are safe in programs but may crash the pretty printer
in the toplevel.



             reply	other threads:[~2011-04-12 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 18:19 John Carr [this message]
2011-04-12 18:21 ` Raoul Duke

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=201104121819.p3CIJlw8019462@outgoing.mit.edu \
    --to=jfc@mit.edu \
    --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).