I'd like to put an end to this thread.
Taking into account everyone's opinion I think the best solution is to go for StudlyCaps with OOP code.
Main reasons:
a) PEAR.
b) Interface with other OO models.
c) Status quo today with iterator and array access interfaces.
I don't think it's such a big deal, and although I slightly preferred underscores, I think it's the best to leave this issue go and finalize on StudlyCaps. As internals@ was pretty much split on this (probably with a slight advantage to StudlyCaps) I think it's the right way to go or we'll never get any closure. Having this rule will give us consistency across PEAR and PHP.
On another subject, Beta 3 is extremely close. I am just waiting for a few engine bugs to be nuked so please commit your final patches.
Thanks, Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
