Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26313
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.194 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=fs78flhZRaITf/eP3y3I88JyU2WykpPGXOVZC0Pm3mAy0Cx1Y7VECmQt3dqd4aIlVMbaQeZsihl9RRhiTH8sg2ew6Ncey0YjO+arNfb0+T4NRlc7x6AdcUrVjaNQYr3G0aSNTtnvBqRXdQjmvMIQKsPEMrTh6j6CcJC7Ux8XNN4=
In-Reply-To: <005e01c6ff82$e6092c30$ec01010a@intranet.db>
References: <005e01c6ff82$e6092c30$ec01010a@intranet.db>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <2FAA3BA3-283C-445D-9648-70C207FF2251@prohost.org>
Cc: <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Date: Fri, 3 Nov 2006 15:14:43 -0500
To: Mauro N. Infantino <mauroi@digbang.com>
Sender: Ilia Alshanetsky <iliaal@gmail.com>
Subject: Re: [PHP-DEV] New Datetime class problem
From: ilia@prohost.org (Ilia Alshanetsky)


On 3-Nov-06, at 3:01 PM, Mauro N. Infantino wrote:

> Hi all,
>
> In our current codebase for PHP5.1 we've a class named  
> 'Datetime' (I suppose
>
> a lot of people is in the same situation). I'm wondering if there's  
> any
> chance
> to add an ini directive in order to disable the definition of the  
> new class.

Nil to none.

> I mean, we had a lot of PHP4 projects and, with two or three minor  
> changes
> we
> got them working in PHP5 (as a matter of fact, we didn't experience  
> almost
> any
> BC trouble... It was kind of easy). How could it be more difficult to
> upgrade
> from PHP5.1 to PHP5.2? It would be a nightmare too change every date
> creation,
> and, of course, the type hints. I'd really like to move to PHP5.2  
> because it
>
> has a lot of really nice things.

Avoid common namespaces and you'll make your application futureproof.  
When developing a distributed application it is always a good idea to  
prefix functions/class names with app name or some acronym to avoid  
overly long names. The way things are going you are going to see more  
and more classes being introduced by "core" PHP as well as the  
growing number of PECL extensions out there and I am not even going  
to mention the thousands of libraries out there.

Ilia Alshanetsky

P.S. If you absolutely must disable it, edit the source code and  
rename the native class to DateTime2 or something similar.