Hi!
Its not a matter of consistency - Properties, as a cross-language concept are not meant to work that way. You need to think of a property as a set
Meant by whom? Is there some law of universe that prevents us from implementing the feature?
of two methods that just have a pretty syntax. Methods cannot be unset, and nor should properties be allowed to. isset() should simply tell us whether a property with the specified name is part of the class or not.
If you need methods, why not use methods? If you mimick object properties, however, it makes sense to make them work exactly like property, otherwise you have to explain why they don't work this way.
isset() in the way you suggest would just be confusing. It would allow is to say that a property does not exist, when in fact it does exist. This is not logical.
Sorry, from your answer I don't understand - what happens when you call isset($foo->property) and unset($foo->property)?
-- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
