From: Oleg Trott <oleg_trott@columbia.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Type Safety and Interruptions
Date: Wed, 13 Aug 2003 00:10:40 -0400 [thread overview]
Message-ID: <200308130010.40500.oleg_trott@columbia.edu> (raw)
Hi
Are there any guarantees about type safety even when program execution is
interrupted?
As a simple example, suppose f is a function that modifies its argument
(array) frequently, x is some value, and I type in the toplevel:
# (* ..... *)
# let a = Array.make 100000 x;;
# f a;;
Interrupted.
and interrupt it before f finishes. Is it at all possible for array "a" to
be in some odd state when its `value' is inconsistent with its type?
What if "f" also contains calls to foreign (C/FORTRAN) functions?
Thanks in advance
--
Oleg Trott <oleg_trott@columbia.edu>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2003-08-13 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 4:10 Oleg Trott [this message]
2003-08-18 12:40 ` Xavier Leroy
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=200308130010.40500.oleg_trott@columbia.edu \
--to=oleg_trott@columbia.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