Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:33726 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47894 invoked by uid 1010); 5 Dec 2007 10:08:13 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 47879 invoked from network); 5 Dec 2007 10:08:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Dec 2007 10:08:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=ron@Opus1.COM; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ron@Opus1.COM; sender-id=unknown Received-SPF: pass (pb1.pair.com: domain Opus1.COM designates 192.245.12.8 as permitted sender) X-PHP-List-Original-Sender: ron@Opus1.COM X-Host-Fingerprint: 192.245.12.8 Viola.Opus1.COM OpenVMS 7.2 (Multinet 4.3-4.4 stack) Received: from [192.245.12.8] ([192.245.12.8:2106] helo=Viola.Opus1.COM) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B3/64-20707-B8876574 for ; Wed, 05 Dec 2007 05:08:12 -0500 Received: from [192.168.1.16] ([24.21.169.102]) by Opus1.COM (PMDF V6.2-X27 #9830) with ESMTPSA id <01MOIL455NWO9L9U7W@Opus1.COM> for internals@lists.php.net; Wed, 05 Dec 2007 03:08:07 -0700 (MST) Date: Wed, 05 Dec 2007 02:08:05 -0800 In-reply-to: To: Robert Lemke Cc: PHP Developers Mailing List Message-ID: <6C783BAF-1E52-44C3-AC07-C741016E9354@opus1.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.752.2) Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7bit X-Gpgmail-State: !signed References: Subject: Re: [PHP-DEV] RFC: Dropping Namespace From: ron@Opus1.COM (Ronald Chmara) On Dec 5, 2007, at 12:52 AM, Robert Lemke wrote: > Hi Derick, > I also agree with your arguments - beautifying class names is not > reason enough for > introducing namespaces. > On 04.12.2007 at 23:16 Derick Rethans wrote: > >> 4. What is wrong with simple prefixes in the first place? Both >> PEAR_*, >> Zend_*, ezc*, and ezp* are perfectly acceptable markers for >> different >> 'namespaces'. We could optionally create a registry on php.net for >> this to avoid conflicts. > > While experimenting with namespaces to use with the next major > version of > TYPO3, I realized that always using a full class name such as > > "T3_MyPackage_MySubPackage_Controller_DefaultController" > > has many advantages. Autoloading becomes a lot easier and if the > filename > equals the class name (ie. the full name, not only > "DefaultController.php") > you are never in doubt where a file belongs to or comes from. > > Therefore we in the TYPO3 project currently tend to not using > namespaces > even if PHP6 had support for them. Wow, total Deja Vu. http://www.phpbuilder.com/lists/php-documentation-list/2001071/0109.php I, for one, would not enjoy typing out: "T3_MyPackage_MySubPackage_Controller_DefaultController" any more often than I absolutely *had* to. And in a somewhat amusing sense, the "register_global" vs. "local variable" debates aren't that far off from "register_class_as_global" vs. "local class namespace" debates.... Maybe we could all just re-read the email archives from back then, and save ourselves a lot of arguing? :) -Bop