And last but not least, I fully agree with Andi and you, the needs of classes internally is growing, faster than ever before. We have to define rules or conventions.
Up until now extensions have been allowed to use their own name to prefix functions within them and as classnames, and that kind of _is_ a convention - isn't it?
However I don't think that discussing it right before a RC release is the right time.
There's never going to be a right time at this rate. There hasn't been a 'right time' in the last 7 months.
We better have to remove the controversial part (drop
the class, keep the functions)
Collective punishment for the users waiting for a fully-fledged Date object that was promised in 5.1.0?
and take the time to discuss this problem, generally and not only for Date.
If PHP 6 is going to introduce class namespaces it's pretty much a temporary problem, no? Again, I have the feeling I'm missing something.
- Steph
Cheers, --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
