Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20515
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <43884194.1020000@lsces.co.uk>
Date: Sat, 26 Nov 2005 11:05:56 +0000
Organization: L.S.Caine Electronic Services
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915
MIME-Version: 1.0
To: internals@lists.php.net
References: <4387E97B.4040300@prohost.org> <4387FC1E.5050207@lerdorf.com>
In-Reply-To: <4387FC1E.5050207@lerdorf.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Solution to date issue in 5.1
From: lester@lsces.co.uk (Lester Caine)

Rasmus Lerdorf wrote:

> 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.
> 
> I don't think choosing a precedent for a class naming convention should 
> be done under duress like this.  I say just ifdef it back out then and 
> put those constants back as they were before.  This class doesn't buy us 
> anything.  It's just a forward-looking thing that really shouldn't go in 
> unless we can all agree on what it is we are looking forward at.

I strikes me that there is a more subtle problem here which goes beyond 
just renaming Date, since we have had a period where people ARE building 
their own libraries with their own classes. So while the current niggle 
is Date, any new core class can potentially cause a problem. Before we 
have any movement forward, a agreed method of ring fencing core classes 
has to be sorted out since this was not implemented previously?

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services
Treasurer - Firebird Foundation Inc.