Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:28310 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17491 invoked by uid 1010); 9 Mar 2007 17:16:47 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 17476 invoked from network); 9 Mar 2007 17:16:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Mar 2007 17:16:47 -0000 Authentication-Results: pb1.pair.com header.from=ralph@smashlabs.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=ralph@smashlabs.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain smashlabs.com from 67.15.58.61 cause and error) X-PHP-List-Original-Sender: ralph@smashlabs.com X-Host-Fingerprint: 67.15.58.61 openrce.org Received: from [67.15.58.61] ([67.15.58.61:49664] helo=SMASHER.SMASHlabs.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 35/16-00491-C7691F54 for ; Fri, 09 Mar 2007 12:16:45 -0500 Received: (qmail 29204 invoked from network); 9 Mar 2007 11:16:41 -0600 Received: from mail1.tippingpoint.com (HELO ?152.67.136.72?) (66.179.208.36) by smashlabs.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 9 Mar 2007 11:16:41 -0600 Message-ID: <45F1965A.5050901@smashlabs.com> Date: Fri, 09 Mar 2007 11:16:10 -0600 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: internals References: <45F076AE.8010001@smashlabs.com> <45F07834.1020801@zend.com> <45F07AA2.9060007@smashlabs.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Class name clashing From: ralph@smashlabs.com (Ralph Schindler) Derick Rethans wrote: > > You should prefix your classes in the first place, as per: > http://www.php.net/manual/en/userlandnaming.php > especially point 1 of: > http://www.php.net/manual/en/userlandnaming.rules.php > In the end (After reading the page on smalltalk), I concede. Stanislav makes some excellent points.. and while this is an annoyance, I agree I can (as well as other developers) be a little more creative in class/method naming to not find themselves in an issue with clashing. That being said: I still think there exists validity in figuring out if adding a layer of 'user context' to the tokenizer/parser would be an interesting project. I would be interested to see if a) it could be done, and b) if it could be done with minimal impact on performance.. Which I have to say, is a key reason I have chosen PHP as a devlopment platform. I also think having a context aware parser/tokenizer would segue into namespacing, which I have also heard could be a feature in the future of PHP.. Either way, I am dropping this for now, but perhaps when I can dedicate some time to the 'C frame of mind', I'll start poking around in php-source again. In any case, thanks, -ralph