* Thus wrote Daniel Schierbeck: > I think this basically sums up the problems of the current handling of > existence-checking in overloaded objects: We have an object that has > user-defined methods for getting and setting object properties (__get() > and __set(), respectively). These methods get and set the properties in > a private array (private: can only be access from within the object > itself). Example (mostly stolen from php.net):
The issue of isset() on __get and __set, will most likely be fixed with 5.1. Curt -- The above comments may offend you. flame at will. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
