Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20588
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
In-Reply-To: <43884194.1020000@lsces.co.uk>
References: <4387E97B.4040300@prohost.org> <4387FC1E.5050207@lerdorf.com> <43884194.1020000@lsces.co.uk>
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <d20df556150d510931bf2433ce1b5263@gravitonic.com>
Content-Transfer-Encoding: 7bit
Cc: internals@lists.php.net
Date: Sat, 26 Nov 2005 13:13:42 -0800
To: Lester Caine <lester@lsces.co.uk>
Subject: Re: [PHP-DEV] Solution to date issue in 5.1
From: andrei@gravitonic.com (Andrei Zmievski)

It seems to me that the only usable method of "ring fencing" core 
classes for the long term is to use namespaces. However, the namespaces 
feature is a fairly large one and obviously will not be in 5.1. We can 
discuss its inclusion in 5.2, should it happen to come out, or in PHP 
6, but we  need to get out 5.1.1 _now_.

- Andrei

On Nov 26, 2005, at 3:05 AM, Lester Caine wrote:

> 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?
>