On 11/25/05, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> Does this include anytime a new function/class is added we need to make
> a prominent notice about since it reserves some name space?
Yes of course, especially if it's such an obvious name like "date".
As opposed to some statements on this list, I would argue that the
global namespace should be reserved for ("owned by") those who write
PHP applications and _not_ for the PHP core developers.
Especially for a language like PHP, where everything is in the core
and no namespaces or packages exist.
How am I supposed to know what class names PHP decides to capture tomorrow?
> So, assuming your old applications are totally future proof is naive.
Well, that's exactly what my customers expect from the software we
develop for them. And btw, maybe it's part of what "enterprise-ready"
is about. I admit that 100% future proofness can never be achieved.
But every break of it it should be carefully considered. And I'm
pretty sure that in the end, companies will go for the platform that
offers the best future proofness of their applications.
Regards
Sebastian
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
