[Zope-dev] Extension class and __init__

Adrian Hungate adrian@haqa.co.uk
Sat, 27 Jul 2002 01:36:06 +0100


Erm... that trashes the concept of mixin's, doesn't it? I mean, if I have a
mixin, that happens to need some initialization (Probably not as uncommon as
people seem to think), then what do I have to do, have a single non-EC class
that groups all the mixin's, then create a subclass combining my ECbase and
my MultiMixinCombinedBase ??? Seems a little convoluted to me, and generally
speaking, convoluted is bad.

Adrian...

--
Adrian Hungate
EMail: adrian@haqa.co.uk
Web: http://www.haqa.co.uk

----- Original Message -----
From: "Lennart Regebro" <lennart@torped.se>
To: "Ross Boylan" <RossBoylan@stanfordalumni.org>; <zope-dev@zope.org>
Sent: Friday, July 26, 2002 11:29 PM
Subject: Re: [Zope-dev] Extension class and __init__


> From: "Ross Boylan" <RossBoylan@stanfordalumni.org>
> > What if you have more than one base class with the method defined?
> > The implication of th example is that the non-extension class base
> > class is used (though even that is not clear; would this work if Base
> > had __init__?), but what if there are several non-extension base
> > classes?
>
> In my experience you simply shouldn't have several non-extension base
> classes.
>
>
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )
>