Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20501 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60619 invoked by uid 1010); 26 Nov 2005 06:50:56 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 60603 invoked from network); 26 Nov 2005 06:50:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Nov 2005 06:50:56 -0000 X-Host-Fingerprint: 65.9.87.49 adsl-9-87-49.mia.bellsouth.net Received: from ([65.9.87.49:21631] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 62/AB-56276-FC508834 for ; Sat, 26 Nov 2005 01:50:55 -0500 To: internals@lists.php.net,Greg Beaver Message-ID: <438805CC.5090806@gmail.com> Date: Sat, 26 Nov 2005 01:50:52 -0500 User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 References: <7.0.0.16.2.20051124161240.0573e640@zend.com> <90.0E.56276.6D207834@pb1.pair.com> <200511251419.56809.pookey@pookey.co.uk> <57.B8.56276.65B27834@pb1.pair.com> <73998811.20051125204046@marcus-boerger.de> <438782C6.80008@gmail.com> <43878626.5060300@lerdorf.com> <512771162.20051125225926@marcus-boerger.de> <43878C41.4030205@gmail.com> <43878D08.4020105@lerdorf.com> <43879039.5070805@gmail.com> <43880213.3020204@php.net> In-Reply-To: <43880213.3020204@php.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 65.9.87.49 Subject: Re: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands of apps out there) From: jrhernandez05@gmail.com (Jessie Hernandez) Greg Beaver wrote: > Jessie Hernandez wrote: > >>1) Do not allow constants in namespaces, just stick to functions and >>classes. > > > I am confused as to why we need namespaced constants. Now that we have > class constants, this is a far better way to "namespace" constants. I > was also under the impression that this was far more efficient than > using define() because it can almost always be evaluted at compile-time. > > Greg We don't! Putting constants in classes is fine for me. I have no problem with removing constants support from my patch. I only added them because I saw them in the Meeting Notes page that was prepared by, well what do you know?, DERICK. I guess that requirement can be, uhm, "#ifdef'ed out", LOL! Just joking, Derick :-)! Regards, Jessie