The point was intended to include only dynamically typed languages (i.e. Ruby with its duck typing). In other words, the risk of naming incompatible methods with the same name only exists if the language will assume these similarly named methods denote polymorphic behavior. In contrast, with a statically typed language like Java, polymorphism will only be assumed if the classes are explicitly placed in a class hierarchy using inheritance. (Unless, of course that is bypassed using reflection, as with Java Beans).
http://bestbody-piercing.com http://bestmedical-tests.com http://charmssale.com http://shop-sextoys.com http://v-jewelrystores.com http://bestgift-baskets.com http://bestprogressiveinsurance.com http://cheap-uggboots.biz http://cheap-uggboots.info http://cheap-uggboots.com http://v-debtconsolidation.info http://v-debtconsolidation.net http://v-debtconsolidation.com http://v-homebusinesses.info http://v-homebusinesses.com http://v-homebusinesses.biz