From: "Nicolas Cannasse" <warplayer@free.fr>
To: "Vitaly Lugovsky" <vsl@ontil.ihep.su>
Cc: "Caml-list" <caml-list@inria.fr>
Subject: Re: [Caml-list] Q: safe language
Date: Fri, 30 Aug 2002 16:48:27 +0200 [thread overview]
Message-ID: <002101c25034$4f17da80$bd00a8c0@mini2k> (raw)
In-Reply-To: <Pine.LNX.4.33.0208301818100.2776-100000@ontil.ihep.su>
> > So for
> > example, C is not safe because you can derefence a bad pointer etc. and
> > cause a seg fault.
>
> Run C in a bytecode "safe" environment (there are some C implementations
> with this functionality) - and it will become a "safe language"?
True.
If you choose the following definition "safe : which does not fail" then you
have
C < "safe" C < Lisp < OCaml
But you can't ensure the total safety of your program without using a
theorem prover such as COQ.
Simple OCaml sample :
List.hd [];;
Nicolas Cannasse
-------------------
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:48 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 [this message]
2002-08-30 15:31 ` Vitaly Lugovsky
2002-08-30 14:55 ` Mike Lin
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='002101c25034$4f17da80$bd00a8c0@mini2k' \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--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;
as well as URLs for NNTP newsgroup(s).