ramifications of such a change. For example, how many PEAR packages might we break with this? Are any of them perhaps even in the php5 tarball itself?
I know this is just an example, but just to clarify:
PEAR is currently taking a bit of a wait and see approach with php5 for obvious reasons. We are mainly looking at the BC breaks atm, so there are really few packages that have moved to php5 only (afaik only PHPUnit2 and SOAP2, which both havent reached a stable state yet). Beyond that the biggest problem I can see PEAR facing with php5 are non studlyCaps API's since then we have to wrap those API's even if we actually just want to extend them, since our CS is studlyCaps.
Beyond that I want to make clear that I am in no position to vote on anything on internals@ due to my lack of direct involvement with the php source itself.
regards, Lukas Smith
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
