Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38019 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14554 invoked from network); 31 May 2008 12:10:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 May 2008 12:10:49 -0000 Authentication-Results: pb1.pair.com header.from=sv_forums@fmethod.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=sv_forums@fmethod.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error) X-PHP-List-Original-Sender: sv_forums@fmethod.com X-Host-Fingerprint: 69.16.228.148 unknown Linux 2.4/2.6 Received: from [69.16.228.148] ([69.16.228.148:36719] helo=host.fmethod.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/B5-02182-94041484 for ; Sat, 31 May 2008 08:10:49 -0400 Received: from [83.228.56.37] (port=3817 helo=pc) by host.fmethod.com with esmtpa (Exim 4.68) (envelope-from ) id 1K2Pv2-00089Y-JR for internals@lists.php.net; Sat, 31 May 2008 07:10:45 -0500 Message-ID: To: Date: Sat, 31 May 2008 15:10:35 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01C8C330.7A62F010" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.fmethod.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - fmethod.com Subject: Alternative to multiple namespaces per file From: sv_forums@fmethod.com ("Stan Vassilev | FM") ------=_NextPart_000_0036_01C8C330.7A62F010 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Hi, I suppose this has been discussed before, so I'll not repeat reasons = unless requested, but I just want to offer a possible feature to = mitigate the impact of "one namespace per file", which doesn't have = controversial syntax and hopefully less difficulties in the = implementation: class Fully::Qualified::Class::Name::Declaration { .... } same as: namespace Fully::Qualified::Class::Name; class Declaration { .... } ... except of course this allows classes of different namespaces to be = declared in one file. Most namespace-enabled languages consider the = above declarations equivalent. Share your opinions. Regards,=20 Stan Vassilev ------=_NextPart_000_0036_01C8C330.7A62F010--