From: Mike Lin <mikelin@MIT.EDU>
To: Vitaly Lugovsky <vsl@ontil.ihep.su>
Cc: J Farrand <farrand@cs.bris.ac.uk>, David Frese <dfrese@dfrese.de>,
SooHyoung Oh <shoh@duonix.com>, Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Q: safe language
Date: 30 Aug 2002 10:55:56 -0400 [thread overview]
Message-ID: <1030719358.1293.3589.camel@mlin> (raw)
In-Reply-To: <Pine.LNX.4.33.0208301818100.2776-100000@ontil.ihep.su>
> Ok, fixed. But I don't see any difference between segfault and NIL passed
> as file descriptor. Program fails - and it does not matter, was it "low
> level" fault or unhandled exception or uncorrect behaviour.
It makes a big difference if you're running in a realtime system with a
shared memory model.
> Okee. Lisp execution environment is safe. Java execution environment is
> safe. C execution environment could be safe. But C is not a safe language,
> as well as Java and Lisp.
The meaning of "safe" is completely nebulous here. Type safety is
provided very well by OCaml. But then we have things like
# max_int;;
- : int = 1073741823
# max_int + 1;;
- : int = -1073741824
Obvious performance and practicality concerns preclude checking the
bounds on every addition operation. Nonetheless, this could without much
stretch of the imagination be called "unsafe".
-Mike
-------------------
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 prev parent reply other threads:[~2002-08-30 14:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 1:36 SooHyoung Oh
2002-08-30 8:41 ` sebastien FURIC
2002-08-30 12:44 ` Vitaly Lugovsky
2002-08-30 13:05 ` David Frese
2002-08-30 13:46 ` Oleg
2002-08-30 16:09 ` Yutaka OIWA
2002-08-30 13:49 ` Vitaly Lugovsky
2002-08-30 14:04 ` J Farrand
2002-08-30 14:26 ` Vitaly Lugovsky
2002-08-30 14:48 ` Nicolas Cannasse
2002-08-30 15:31 ` Vitaly Lugovsky
2002-08-30 14:55 ` Mike Lin [this message]
2002-08-30 14:58 ` Eric Newhuis
2002-08-30 16:03 ` Yutaka OIWA
2002-08-30 21:44 ` Oliver Bandel
2002-09-01 8:07 ` John Max Skaller
2002-08-30 14:50 ` David Frese
2002-08-30 15:38 ` Vitaly Lugovsky
2002-08-30 15:28 ` didier plaindoux
2002-08-30 14:41 ` Florian Hars
2002-08-30 14:42 ` Nicolas Cannasse
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=1030719358.1293.3589.camel@mlin \
--to=mikelin@mit.edu \
--cc=caml-list@inria.fr \
--cc=dfrese@dfrese.de \
--cc=farrand@cs.bris.ac.uk \
--cc=shoh@duonix.com \
--cc=vsl@ontil.ihep.su \
/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