Object orientation - can you have too much of a good thing?

Igor Stasenko siguctua at gmail.com
Mon Oct 29 19:43:22 UTC 2007


There is a language which uses multiple-dispatch. See Slate. And it is
object-oriented.

I don't see how given problem (lack of multiple dispatch) could be
considered as a OO problem, or as an example against using OO
principles.
An OO principles is simple: associate some state with behavior. It's
always a developer's decision, what to hide and what to make public in
his model.

-- 
Best regards,
Igor Stasenko AKA sig.



More information about the Squeak-dev mailing list