Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26311 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38191 invoked by uid 1010); 3 Nov 2006 20:01:58 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 38176 invoked from network); 3 Nov 2006 20:01:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Nov 2006 20:01:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=mauroi@digbang.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mauroi@digbang.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain digbang.com from 200.59.46.140 cause and error) X-PHP-List-Original-Sender: mauroi@digbang.com X-Host-Fingerprint: 200.59.46.140 mx.digbang.com Linux 2.5 (sometimes 2.4) (4) Received: from [200.59.46.140] ([200.59.46.140:50878] helo=mx.digbang.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4F/2A-07680-130AB454 for ; Fri, 03 Nov 2006 15:01:55 -0500 Received: (qmail 7611 invoked by uid 89); 3 Nov 2006 19:50:38 -0000 Received: by simscan 1.2.0 ppid: 7593, pid: 7602, t: 0.1614s scanners: attach: 1.2.0 clamav: 0.88.5/m:40/d:2156 Received: from unknown (HELO bensimon) (mauroi@digbang.com@200.127.112.162) by mx.digbang.com with ESMTPA; 3 Nov 2006 19:50:38 -0000 To: Date: Fri, 3 Nov 2006 17:01:48 -0300 Message-ID: <005e01c6ff82$e6092c30$ec01010a@intranet.db> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acb/guV1eucBxUYDRrKFHWsWtA+i9A== Subject: New Datetime class problem From: mauroi@digbang.com ("Mauro N. Infantino") 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. 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. Thanks. Regards, Mauro.