From: skaller <skaller@users.sourceforge.net>
To: rossberg@ps.uni-sb.de
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Unsoundness is essential
Date: Fri, 05 Oct 2007 05:56:15 +1000 [thread overview]
Message-ID: <1191527775.7078.67.camel@rosella.wigram> (raw)
In-Reply-To: <59808.84.159.34.129.1191520580.squirrel@www.ps.uni-sb.de>
On Thu, 2007-10-04 at 19:56 +0200, rossberg@ps.uni-sb.de wrote:
> skaller wrote:
> >
> > All advanced programming languages have unsound type systems
> > of necessity. Some falsely claim soundness by denying the
> > expression of certain type information (eg array bounds
> > or the type of integers excluding zero).
>
> No. Soundness is the absence of /untrapped/ errors.
Fair ..
> Exceptions are /trapped/ errors.
I chose not to accept that definition. I use instead
"trapped at compile time", meaning "in advance of running
the program".
Otherwise you could say dynamically typed languages were
strongly typed and sound.
I'm not saying that it is a bad thing to emit code to
generate diagnostics at run time, if you can't prove
safety at compile time .. I AM saying that doing that
means the type system is unsound, because by type system
I mean "static type checking".
The point is that static checks are hopefully rigorous:
what ever properties they ensure they ensure them
for certain, once and for all time.
Whereas dynamic checks prove only, in some cases,
that there is a bug and thus you have to actually
test the program with good coverage, and even then
you learn little UNLESS there is a bug :)
Also note, specified exceptions are not suitable traps:
this is a conformance issue and not really related,
but it is worth noting that if a catchable exception
is specified, the condition that caused it to be raised
isn't necessarily an error:
try:
x = "Bad" +42
except:
print "Python WILL print this"
This code is perfectly well defined and contains no
errors, not even a type error. Adding a string to an integer
raises TypeError in Python, and this is mandatory, so this
behaviour is well defined and can be used as a programming
technique (and it is!), there is no 'trapped' error here.
C/C++ does this right: if a program is 'ill-formed' then
a diagnostic must be issued. Throwing an exception silently
is NOT allowed. [C/C++ doesn't mandate diagnostics always because
some are too hard to detect]
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-10-04 19:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 8:35 Locally-polymorphic exceptions [was: folding over a file] oleg
2007-10-03 11:27 ` kirillkh
2007-10-03 11:48 ` [Caml-list] " Daniel de Rauglaudre
2007-10-03 12:19 ` kirillkh
2007-10-03 12:32 ` Daniel de Rauglaudre
2007-10-03 14:34 ` kirillkh
2007-10-03 20:39 ` Christophe Raffalli
2007-10-03 22:50 ` Unsoundness is essential skaller
2007-10-03 23:13 ` [Caml-list] " Jacques Carette
2007-10-04 1:24 ` skaller
2007-10-04 11:26 ` David Allsopp
2007-10-04 12:45 ` Vincent Hanquez
2007-10-04 15:07 ` skaller
2007-10-03 23:13 ` Vincent Aravantinos
2007-10-04 1:49 ` skaller
2007-10-03 23:28 ` Joshua D. Guttman
2007-10-04 1:52 ` skaller
2007-10-04 2:35 ` Brian Hurt
2007-10-04 7:46 ` Christophe Raffalli
2007-10-04 8:56 ` Arnaud Spiwack
2007-10-04 14:49 ` skaller
2007-10-04 15:00 ` Harrison, John R
2007-10-04 15:29 ` Andrej Bauer
2007-10-04 16:25 ` skaller
2007-10-04 18:17 ` Arnaud Spiwack
2007-10-04 20:54 ` skaller
2007-10-04 22:24 ` Arnaud Spiwack
2007-10-04 16:37 ` skaller
2007-10-04 18:59 ` Christophe Raffalli
2007-10-04 15:04 ` Andrej Bauer
2007-10-04 15:57 ` Christophe Raffalli
2007-10-04 16:03 ` skaller
2007-10-04 20:02 ` Ken Rose
2007-10-04 21:00 ` skaller
2007-10-04 15:31 ` Lukasz Stafiniak
2007-10-04 17:56 ` rossberg
2007-10-04 19:56 ` skaller [this message]
2007-10-04 21:07 ` rossberg
2007-10-04 22:23 ` skaller
2007-10-05 2:48 ` Bárður Árantsson
2007-10-04 2:16 ` Locally-polymorphic exceptions [was: folding over a file] oleg
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=1191527775.7078.67.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=rossberg@ps.uni-sb.de \
/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).