Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20641
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7D.A7.56276.75789834@pb1.pair.com>
To: internals@lists.php.net
Date: Sun, 27 Nov 2005 11:15:48 +0100
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
References: <4387E97B.4040300@prohost.org>
In-Reply-To: <4387E97B.4040300@prohost.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Solution to date issue in 5.1
From: lsmith@php.net (Lukas Smith)

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.

I do not think it makes sense for PHP to start prefixing internal 
classes with PHP. We just need a solid userland naming guide so that PHP 
can keep the right-of-way for internal naming.

As for PEAR if we find better ways of cooperating on the API level it 
would be a nice dream, however the reality is that API's are a matter of 
taste and traditionally PEAR developer tastes are radically different 
from internals developers. This is also due to the fact that PEAR API's 
are generally designed for completeness, flexibility and extensibility, 
where as it seems to be that internals traditionally mainly designs for 
simplicity. This again leads to the conclusion that PEAR needs to prefix 
just like the rest of the PHP world.

I have attempted to write such a userland naming guide but I am a bit 
scared to post it here as I expect this to result in 100 emails where 
people compete with quantity instead of quality. Anyways if anyone has 
sincere interest in helping please write me offlist. Obviously the 
powers that are need to nod off the final version.

regards,
Lukas