|
![](/i/fill.gif) |
Darren New wrote:
>> Of course, much as I like Smalltalk, the lack of static typing makes
>> it really hard to use. [...] but *good luck* figuring out where the
>> _problem_ is. The
>> call stack only shows you where the problem get _detected_.
>
> You know, I did my PhD work by patching into someone else's structured
> editor/compiler/interpreter written Smalltalk, without really
> understanding all the details. I had this kind of error maybe a handful
> of times, and it was never confusing what happened.
Apparently I'm strange. For me, this is *the* most common class of
errors. (After silly things like typos, at least.) And having to track
down and fix these problems manually seems so tedious when a properly
designed system would have told me exactly what to fix before I even
finished compiling.
>> As soon as you start trying to do anything more sophisticated than
>> that, scripting languages become inadaquate.
>
> I disagree.
It's a free country.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |