Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26353
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain cschneid.com from 195.226.6.42 cause and error)
Message-ID: <454E23DA.8000705@cschneid.com>
Date: Sun, 05 Nov 2006 18:48:10 +0100
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: Ilia Alshanetsky <ilia@prohost.org>
CC:  internals@lists.php.net
References: <005e01c6ff82$e6092c30$ec01010a@intranet.db> <2FAA3BA3-283C-445D-9648-70C207FF2251@prohost.org> <454CBD65.5040205@cschneid.com> <B990B08B-20E3-41FD-BA54-A8F78443B572@prohost.org> <454D66C4.2090708@cschneid.com> <1465A1B3-C0AE-48E0-9E3A-66BDC57D89F3@prohost.org>
In-Reply-To: <1465A1B3-C0AE-48E0-9E3A-66BDC57D89F3@prohost.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] New Datetime class problem
From: cschneid@cschneid.com (Christian Schneider)

Ilia Alshanetsky wrote:
> When we were picking a name the discussion was public on this very list 
> and based on our analysis of what names people were using in their 
> application and what would be an ideal name DateTime was picked. 

I'm not questioning this decision. I'm talking about the policy for 
further classes. Maybe I should change the topic to be clearer...

>> A little thought experiment: Let's assume the number of application 
>> classes (and the usage of those classes) is on average higher than 
>> those of the core classes.  Would that change the situation?
> 
> The number of current users does not matter, simply because are you not 
> comparing equivalent things here. You are comparing existing code to 
> something that just came out.

Forget about all the code out there: Let's say the average application 
uses its own classes 10 times and PHP core classes only 5 times, which 
one should have the right to the short and more convenient name?

And I'm not saying that this is the case, it's just a thought.

>> Come on, that can't be the solution. Think about hosting companies for 
>> example.
> 
> They as a rule use old versions, in fact I bet you'd be hard pressed to 
> find a big or even a medium size hosting company offering PHP 5.2 just 
> now. So you have plenty of time to fix your code.

I could be mean and ask why that is. But that's not the discussion here. 
We're talking about the naming policy of classes in the long run.

Again: I'm not asking to change anything, I'm just mentioning that there 
are different point of views (PHP core centric vs. application centric 
ones) which both have to be recognized.

- Chris