Version franēaise
Home     About     Download     Resources     Contact us    
Browse thread
Locally-polymorphic exceptions [was: folding over a file]
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Bįršur_Įrantsson <spam@s...>
Subject: Re: Unsoundness is essential
skaller wrote:

> On Thu, 2007-10-04 at 23:07 +0200, rossberg@ps.uni-sb.de wrote:
>> skaller wrote:
>>>> 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".
>> As a definition for what?
> 
> What trapped means.
> 
>>> Otherwise you could say dynamically typed languages were
>>> strongly typed and sound.
>> In fact, technically, they are. People have used the term "unityped" for it.
> 
> That isn't what I meant at all. Python is statically unityped, but
> dynamically it has integers, reals, strings, etc. Type errors
> in Python are not 'trapped' .. they're impossible.
> 

$ python
Python 2.5.1 (r251:54863, Oct  1 2007, 21:44:24)
[GCC 4.1.2 (Gentoo 4.1.2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> 1 + "a"
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
TypeError: unsupported operand type(s) for +: 'int' and 'str'

-- 
Bardur Arantsson
<bardurREMOVE@THISscientician.net>

- I may not have morals, but I do have standards.