On 4-Nov-06, at 11:21 PM, Christian Schneider wrote:
Ilia Alshanetsky wrote:
On 4-Nov-06, at 11:18 AM, Christian Schneider wrote:
Ilia Alshanetsky wrote:
Avoid common namespaces and you'll make your application
futureproof.
I'm still wary of this approach because it puts the burden on 99%
of the code to be written (applications) instead of a small,
controllable subset (core and libraries).
Translation: blame other people...
I'm not sure what you mean here. I was just doing a head count on
who has to come up with save names: A few core developers or all of
the PHP users.
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. Google's code search confirms we've made the right decision
as it would seem there are only about 8 results for applications
already misusing that namespace.
s more popular and as such needs of many outweigh needs of the few.
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.
You can use old PHP too, or modify the source code, it is "open
source" after-all.
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.
Ilia Alshanetsky
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
