|
But why would you want to offer that? Surely the point of putting code
in a framework is so that a developer doesn't need need to go down that
path. All it would provide (as I can see) is the ability to create a
smaller array with which to do the search for isset. graeme. David Zülke wrote: It's protected to allow sublasses to implement the singleton functionality themselves. You cannot redeclare a private member, and $instance is the common name for the instance variable.- David-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of graeme Sent: Saturday, July 02, 2005 11:25 AM To: 'Agavi Development' Subject: [agavi-dev] Singleton Just had a peek at the code for SingletonModel. (revision 151) I think the $instance array should be private. Only that class wants to be able to manage the array list whilst, yes constructors should be protected allowing the subclasses to modify the constructor. graeme. _______________________________________________ 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 |
_______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
