🚀 go-pugleaf

In article <879@puck.mrcu> paj@uk.co.gec-mrc (Paul Johnson) writes:
>On the other hand I am interested in the assertion that type errors
>are rare in Smalltalk development.  Does anyone have any statistics to
>back this up?  

Well, I have one statis. :-)    My dissertation project is implemented in
Smalltalk.  I've been working on it for four years or so, and I've gotten
three types of type-mismatch errors (i.e., "message not understood"):

1) Looked up a name in the wrong dictionary, didn't check the result
because I "knew" it would always be there, sent the result (nil,
because it wasn't found) a message, and "nil" didn't understand it.
Not a type error because the problem was the wrong dictionary, not the
wrong type. Some other runtime error (subscript out of bounds, say)
would have happened in another language.

2) Sent a message to a string instead of to the result of looking up
that string in a dictionary.  Always caught on the first test run.

3) Sent a message to an object which should have implemented that
message but didn't because I didn't think it would be called on this
particular test run. Always caught the first time.

In summary, "wrong type" errors just never really came up because they
were the wrong type except number 2. In that case, it was always
invariably caught on the first run of that method. 
      -- Darren
-- 
--- Darren New --- Grad Student --- CIS --- Univ. of Delaware ---
----- Network Protocols, Graphics, Programming Languages, FDTs -----
  +=+=+ My time is very valuable, but unfortunately only to me +=+=+
+ When you drive screws with a hammer, screwdrivers are unrecognisable +