From: J Farrand <farrand@cs.bris.ac.uk>
To: Vitaly Lugovsky <vsl@ontil.ihep.su>
Cc: David Frese <dfrese@dfrese.de>, SooHyoung Oh <shoh@duonix.com>,
Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Q: safe language
Date: Fri, 30 Aug 2002 15:04:07 +0100 (BST) [thread overview]
Message-ID: <Pine.GSO.4.33.0208301500340.14264-100000@hua> (raw)
In-Reply-To: <Pine.LNX.4.33.0208301746580.2776-100000@ontil.ihep.su>
On Fri, 30 Aug 2002, Vitaly Lugovsky wrote:
> No. In this place program may be expecting some structure, which can
> contain NIL. There is no other way in lisp to define structures - so, any
> code accepting lists will accept any alien structure. Is is type safety?
> No way! Dynamically typed languages can't be safe.
"Safe" is not the same as "Type Safe". ISTR safe means that a program
written in the language will not cause a machine level error. So for
example, C is not safe because you can derefence a bad pointer etc. and
cause a seg fault. LISP is safe. Even though you can apply a function to
arguments of the wrong type, LISP has well defined behaviour for dealing
with this. (That behaviour might just be that the runtime prints an error
a halts the program, but still better than what C would do, which is
basically anything...)
--
Jim Farrand, ML Group, mailto:farrand@cs.bris.ac.uk
Department of Computer Science, http://www.cs.bris.ac.uk/~farrand
University of Bristol, tel: +44-(0)117-954-5254
Woodland Road, Bristol, BS8 1UB, UK
-------------------
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-31 18:01 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 [this message]
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
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=Pine.GSO.4.33.0208301500340.14264-100000@hua \
--to=farrand@cs.bris.ac.uk \
--cc=caml-list@inria.fr \
--cc=dfrese@dfrese.de \
--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;
as well as URLs for NNTP newsgroup(s).