Darren New <dne### [at] sanrrcom> wrote:
> Works great, as long as they're the same type. Try swapping an array of 
> integers with a socket.

  Wouldn't it break the code which expects the object to be an array, but
the object gets suddenly changed to something completely different?

  (What does Smalltalk do when an inexistent method is called? Runtime error?
That's at least what happens in Objective-C, which is based on the same
principles as Smalltalk, IIRC.)

-- 
                                                          - Warp

Post a reply to this message