Ok.. I see the reasons for keeping initialize(). Mike seems ok with providing the ability to pass params to certain (all?) calls to initialize() methods.. anyone disagree with that piece? --Bob
On 6/19/05, David Zülke <[EMAIL PROTECTED]> wrote: > > So this message has two purposes: > > > > 1. to discuss initialize() vs. __construct(), at least as it relates > > to Models.. possibly other places. > > > > Currently, Agavi uses the initialize() method (basically) instead of > > relying on the __construct() method. Is this necessary, or might we > > simplify things a bit by using the builtin __construct method? I > > realize this would be our first major BREAK in compatibility with > > Mojavi. > > I don't really see a reason why we should do that. One reason why > initialize() is uses might be that you can "drop in" a class without > modifications and use them as a model. There certainly is some redundancy > there, but you know it - never change a running system ;) > > - David > > > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
