Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:33720 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26711 invoked by uid 1010); 5 Dec 2007 08:52:41 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 26696 invoked from network); 5 Dec 2007 08:52:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Dec 2007 08:52:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=robert@typo3.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=robert@typo3.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain typo3.org from 217.72.131.73 cause and error) X-PHP-List-Original-Sender: robert@typo3.org X-Host-Fingerprint: 217.72.131.73 mail.elios.de Linux 2.4/2.6 Received: from [217.72.131.73] ([217.72.131.73:35482] helo=mail.elios.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/F0-20707-5D666574 for ; Wed, 05 Dec 2007 03:52:38 -0500 Received: from [192.168.0.6] (pD9EE4909.dip.t-dialin.net [217.238.73.9]) by mail.elios.de (Postfix) with ESMTP id B6AA150463A for ; Wed, 5 Dec 2007 09:52:34 +0100 (CET) Cc: PHP Developers Mailing List Message-ID: In-Reply-To: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-20--505782854" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Wed, 5 Dec 2007 09:52:29 +0100 References: X-Pgp-Agent: GPGMail d49 (Leopard) X-Mailer: Apple Mail (2.915) Subject: Re: [PHP-DEV] RFC: Dropping Namespace From: robert@typo3.org (Robert Lemke) --Apple-Mail-20--505782854 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit 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. robert -- WE NEED UNICODE! http://typo3.org/gimmefive http://buzz.typo3.org/people/robert-lemke/ --Apple-Mail-20--505782854 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFHVmbRDu+3qCHvGSIRAq/hAKCnfGpXQrLCGur12rxD6IROvx74dQCfSIMb 3fF2NXvECxR6VUwhFjO2zxo= =2AHJ -----END PGP SIGNATURE----- --Apple-Mail-20--505782854--