Hello Andi,
to this i only agree under two conditions. First we remove other like method_exists() too and second we fix handling of implicit public and dynamic properties. Unless the second is done i see such a function as relative important and don't like to use reflection overhead always.
Marcus,
What are you talking about? The fact that method_exists() for past reasons means we should not think of coding standards anymore? The point in time when we decided on internals@ to work in a certain way was looking forward. We didn't start breaking BC and removing lots of non-compliant code and function names (as you know there are many of those in PHP). So BC is an issue and thus, method_exists() won't be removed.
Secondly, for the few instances that someone requires property_exists() I don't see any reason not to use reflection API.
I don't even understand your second "condition". I don't see why we have to work with setting conditions.
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
