On the Studlycaps issue my opinion is that it is a guideline and while it would be nice to have consistency in the end it is ultimately up to the extension authors to decide whether they wish to follow the guideline or not. I have no plans on going back and breaking the few extensions I have written that have OO APIs because I don't think aesthetic changes is worth breaking BC over, but I will probably follow the guideline for new ones.
We could make the decision that we will not bundle any extension that doesn't follow the guidelines although in this case that might not be a good idea. I see 3 ways forward:
1. Stick with the freeze and deal with the inconsistency
2. Remove the freeze, convince Georg to make the change (if possible) and make very sure people realize that RC1->RC2 is not just bug fixes
3. Unbundle mysqli to pecl and let it evolve at its own pace and we can include it in the standard tarball when everyone is happy with it
Guys,
We all know that consistency problems in the past have been a pain in the ass. I'm sure there have been hundreds of emails on internals@ about these issues. All I'm saying is, why shoot ourselves in the foot so early in the game especially as we mentioned studlyCaps in the CODING_STANDARDS. It doesn't really matter if you like studlyCaps or prefer underscores; consistency is the game.
I still think that the right thing to do is to do what's right (change to studlyCaps) and release RC2 as soon as possible (whenever everyone is ready). We will then restart a deep-freeze for new features and will continue to stabilize PHP 5.
But as RM I can't go through every extension in PHP and make sure every last place has been changed but extension authors also have to take responsibility.
And yes, we'll need to change our articles on Zend.com and we'll have to make changes in our PHP 5 book but I think PHP 5 is more important.
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
