Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20498 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59298 invoked by uid 1010); 26 Nov 2005 06:50:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 59283 invoked from network); 26 Nov 2005 06:50:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Nov 2005 06:50:12 -0000 X-Host-Fingerprint: 69.64.38.41 bluga.net Linux 2.5 (sometimes 2.4) (4) Received: from ([69.64.38.41:58035] helo=bluga.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 63/6B-56276-4A508834 for ; Sat, 26 Nov 2005 01:50:12 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by bluga.net (Postfix) with ESMTP id 4253E21CBBA; Sat, 26 Nov 2005 00:51:44 -0600 (CST) Received: from bluga.net ([127.0.0.1]) by localhost (bluga.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30481-07; Sat, 26 Nov 2005 00:51:44 -0600 (CST) Received: from [192.168.1.101] (ftcl002.digis.net [66.17.140.42]) by bluga.net (Postfix) with ESMTP id 9DDF221CBA7; Sat, 26 Nov 2005 00:51:42 -0600 (CST) Message-ID: <4388059C.8060106@php.net> Date: Sat, 26 Nov 2005 00:50:04 -0600 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pierre.php@gmail.com CC: internals@lists.php.net References: <20051126024119.00105e42@localhost.localdomain> In-Reply-To: <20051126024119.00105e42@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new using ClamAV at bluga.net Subject: Re: solution to the "Date" issue From: cellog@php.net (Greg Beaver) Pierre wrote: > On Fri, 25 Nov 2005 18:32:14 -0600 > cellog@php.net (Greg Beaver) wrote: > > >>Hi, >> >>I would like to propose these simple steps be taken: >> >>1) rename "date" to "PHP_Date" >>2) reserve the "PHP_" prefix for all future core classes in PHP 5 (if >>any) 3) when namespaces become available, reserve "PHP" for all future >>internal classes > > > Reread the previous thread, this solution is not acceptable. > > The only safe solution is to put it back in the #ifdef. We have then > time to do the right things and right names in php6. Pierre, you can do all the #ifdefs you want, this idea does not prevent this :). In addition, the #ifdef has no effect on this idea. Greg