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...
When developing a distributed application it is always a good idea
to prefix functions/class names with app name or some acronym to
avoid overly long names. The way things are going you are going to
see more and more classes being introduced by "core" PHP as well
as the growing
... which brings us back to the discussion of namespaces and which
one core classes should use ;-)
The language should ALWAYS have the best names possible to simplify
development, because that means convenience for majority of users. No
matter how popular your app, PHP, the language is still hundreds if
not thousands of times more popular and as such needs of many
outweigh needs of the few.
number of PECL extensions out there and I am not even going to
mention the thousands of libraries out there.
Those are less of a problem because you don't have to include them
if you don't want to.
You can use old PHP too, or modify the source code, it is "open
source" after-all.
Ilia Alshanetsky
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
