no return values for __init__ ??

[Aahz Maruch]

In article <001701bf5b54$e0e110d0$f29b12c2 at secret.pythonware.com>,
Fredrik Lundh <fredrik at pythonware.com> wrote:
>Helge Hess <helge.hess at mdlink.de> wrote:
>>
>> Hm, I wonder why it is simpler to have two separate kinds of methods
>> instead of a consistent behaviour for all methods ?
>
>umm. in my dictionary, "consistent" means "free from variation or
>contradiction".
>
>in the current design, if you call a class object, you *always* get
>an instance of that class. in the current design, if you inherit from
>a class and call the parent's init function, it *always* initializes
>the current instance. in the current design, multiple inheritance is
>*always* supported.
>
>in your design, you've changed "always" to "it depends". hardly
>something that would make Python's behaviour more consistent.

Helge, Fredrik here has done a much better job of illustrating what I
meant by top-view versus bottom-view.  You're focusing on consistency of
method implementation and use (bottom-view); we're focusing on
consistency of the Python model as a whole (top-view).
--
                      --- Aahz (@netcom.com)

Androgynous poly kinky vanilla queer het    <*>     http://www.rahul.net/aahz/
Hugs and backrubs -- I break Rule 6

Have a *HAPPY* day!!!!!!!!!!