Hi!
3) The use case for this function required the existing behavior (i.e. can you safely call property $x from the current scope with no warning?), and that *ignored* when the behavior was changed. We already have Reflection classes for inquiring protected/private properties of a class from any scope.
Maybe we can fix this by having an argument to the function that if false, checks only for existence, and if true, checks also for access? On the other hand, we already have isset() for vars and is_callable() for methods, so this use case might to be covered. -- 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
