Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24479 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45849 invoked by uid 1010); 18 Jul 2006 17:11:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 45834 invoked from network); 18 Jul 2006 17:11:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jul 2006 17:11:17 -0000 X-PHP-List-Original-Sender: steph@zend.com X-Host-Fingerprint: 192.38.9.232 gw2.emini.dk Linux 2.4/2.6 Received: from ([192.38.9.232:2668] helo=gw2.emini.dk) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id DF/53-11992-3DC0DB44 for ; Tue, 18 Jul 2006 12:31:16 -0400 Received: from foxbox (IGLD-83-130-221-199.inter.net.il [83.130.221.199]) by gw2.emini.dk (Postfix) with ESMTP id 177EAB04F2; Tue, 18 Jul 2006 18:31:11 +0200 (CEST) Message-ID: <0b5b01c6aa87$11798000$6602a8c0@foxbox> Reply-To: "Steph Fox" To: "Ilia Alshanetsky" , "Pierre" Cc: "Derick Rethans" , "Lukas Smith" , "PHP internals" References: <44B8BF7C.2060900@php.net> Date: Tue, 18 Jul 2006 18:27:29 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: [PHP-DEV] Re: PHP 5.2 Status Update From: steph@zend.com ("Steph Fox") > On 18-Jul-06, at 12:16 PM, Pierre wrote: > >> On 7/18/06, Ilia Alshanetsky wrote: >>> The date extension functionality can be enabled, but we need to >>> rename the date class to avoid naming conflicts encountered with PHP >>> 5.1. >> >> Wait, you are suggesting to enable this empty class and rename it? And >> then he will rename it again for phph6? That's plain stupid and >> insane. > > No. Derick wants to enable all the code in the date extension > (methods of the date class and so on). The only way I can see us > doing it is by renaming the 2 classes the extension defines to > something that won't cause namespace problems. Hate to be a pain, but _what_ namespace problems? Where were all those bug reports the first time this was enabled? Why hasn't Date in PEAR changed its name to include the PEAR prefix? Aren't these 'namespace problems' so much vaporware? - Steph > > Ilia Alshanetsky