Re: New Datetime class problem

From: Date: Sun, 05 Nov 2006 23:37:42 +0000
Subject: Re: New Datetime class problem
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-26371@lists.php.net to get a copy of this message
Hello, On 11/6/06, Lester Caine <lester@lsces.co.uk> wrote:
Ilia Alshanetsky wrote: The language always has the best pick of namespaces, this is not just PHP, but ANY language. The fact we've made a compromise and allows PEAR to retain the date class IMO has been a horrible mistake, one hopefully not to be repeated in the future.
For the 10^347 times, the problem was/is not Date but the way global namespace and features got in late in the game, without previous warning in any previous PHP release or any announcements. The problem is that we just considered that we can do it whenever we want and how we want, that is the horrible mistake. Things are however getting better, at least for a limited amount of developers who have to justify/explain/change the names they use in their extensions. It will be perfect if this rule applies to anyone and the naming decisions are done before the extension/addition is in a release (RC or final). --Pierre

« previous php.internals (#26371) next »