If you're going to make it an abstract class, why not change the name, too? The "I" presumably means "interface", right?
On Tue, Nov 23, 2010 at 9:53 PM, Matej Knopp <matej.kn...@inmethod.com> wrote: > +1 > > -Matej > > On Tue, Nov 23, 2010 at 9:22 PM, Igor Vaynberg <igor.vaynb...@gmail.com> > wrote: >> +1 >> >> -igor >> >> On Tue, Nov 23, 2010 at 6:22 PM, Igor Vaynberg <igor.vaynb...@gmail.com> >> wrote: >>> the ibehavior interface has become somewhat cluttered and a lot of >>> methods in it can have a nice default implementation that works for >>> 99% of the usecases. there is no longer a point to having it as an >>> interface. this vote is to >>> >>> - rename IBehavior to Behavior and make it an abstract class with >>> stubs for every method >>> - rename AbstractBehavior to BaseBehavior and deprecate it, it has >>> accumulated some crud over the years >>> >>> the only thing we will lose is the ability to cleanly proxy a >>> ibehavior and to use it as a mixin - i cant think of any usecases for >>> either >>> >>> vote ends 7pm gmt-8 friday the 26th >>> >>> -igor >>> >> >
