Re: Solution to date issue in 5.1

From: Date: Sat, 26 Nov 2005 05:39:38 +0000
Subject: Re: Solution to date issue in 5.1
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-20491@lists.php.net to get a copy of this message
I have to ask: what does renaming really buy us? The only purpose of introducing this class in RC6, as far as I can tell, was to reserve the 'Date' name for future use. Since this goal is clearly unachievable, what is the point of keeping a barely functional class around (as PhpDate)? In my opinion, we should remove it (#ifdef it out), and wait until we are ready for the full implementation and can pick a good name, or until we have namespaces and can use them to separate PHP's own classes. - Andrei On Nov 25, 2005, at 8:50 PM, Ilia Alshanetsky wrote:
The attached patch is a possible solution to the date *crisis*, it renames the class to PhpDate to avoid any namespace conflicts with pear or custom user classes called date. If there are no strong objection 5.1.1 (5.1.0 + this patch and nothing else) goes out on Monday.


« previous php.internals (#20491) next »