Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20491
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
In-Reply-To: <4387E97B.4040300@prohost.org>
References: <4387E97B.4040300@prohost.org>
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <9784192ddeca75a1d77f5536f909b957@gravitonic.com>
Content-Transfer-Encoding: 7bit
Cc: internals@lists.php.net
Date: Fri, 25 Nov 2005 21:39:38 -0800
To: Ilia Alshanetsky <ilia@prohost.org>
Subject: Re: [PHP-DEV] Solution to date issue in 5.1
From: andrei@gravitonic.com (Andrei Zmievski)

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.
>