Ilia Alshanetsky wrote:
When we were picking a name the discussion was public on this very list
and based on our analysis of what names people were using in their
application and what would be an ideal name DateTime was picked.
I'm not questioning this decision. I'm talking about the policy for
further classes. Maybe I should change the topic to be clearer...
A little thought experiment: Let's assume the number of application
classes (and the usage of those classes) is on average higher than
those of the core classes. Would that change the situation?
The number of current users does not matter, simply because are you not
comparing equivalent things here. You are comparing existing code to
something that just came out.
Forget about all the code out there: Let's say the average application
uses its own classes 10 times and PHP core classes only 5 times, which
one should have the right to the short and more convenient name?
And I'm not saying that this is the case, it's just a thought.
Come on, that can't be the solution. Think about hosting companies for
example.
They as a rule use old versions, in fact I bet you'd be hard pressed to
find a big or even a medium size hosting company offering PHP 5.2 just
now. So you have plenty of time to fix your code.
I could be mean and ask why that is. But that's not the discussion here.
We're talking about the naming policy of classes in the long run.
Again: I'm not asking to change anything, I'm just mentioning that there
are different point of views (PHP core centric vs. application centric
ones) which both have to be recognized.
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
