Re: [Pyobjc-dev] Calling methods on nil
Brought to you by:
ronaldoussoren
From: Just v. R. <ju...@le...> - 2003-05-08 17:43:40
|
Marcel Weiher wrote: > > "Explicit is better than implicit". > > Not necessarily. For example, the polymorphism you get with OO is > *implicit*. You didn't say which exact method you wanted, you just > sent the message and let the system decide which specific > implementation to use. And yes, there are still a number of people > who consider this 'evil'. Bad example (I'm calling _this_ method on _that_ instance, I don't see what's implicit about that), but of course explicit isn't *always* better than implicit, it's merely a general guideline for how things work in Python (for example "12" + 13 raises an exception in Python, whereas Perl thinks "hey, this string looks like a number, lets treat it like that"). A _good_ counter example is Python's reference counting: it's implicit, yet better than manual ref counting. (To be completely explicit <wink>: in the context of Python at least.) Just |