Along those lines, is there any consideration of adding ::interface and 
::trait, where applicable?

How would this be applicable?

In the context of variables, an object can be only of a single class type, whereas it can be an *instanceof* multiple interfaces (or an extension of other types) or be *composed of* multiple traits (in full or partial if there are trait conflicts.)

How would you get the right semantics out of $object::interface, or $object::trait, and/or do you have an example of what you're expecting?

-ralph

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to