Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43335 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92123 invoked from network); 12 Mar 2009 23:39:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Mar 2009 23:39:37 -0000 Authentication-Results: pb1.pair.com header.from=andrei@gravitonic.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=andrei@gravitonic.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain gravitonic.com from 74.125.46.31 cause and error) X-PHP-List-Original-Sender: andrei@gravitonic.com X-Host-Fingerprint: 74.125.46.31 yw-out-2324.google.com Received: from [74.125.46.31] ([74.125.46.31:9817] helo=yw-out-2324.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4F/7F-30999-73D99B94 for ; Thu, 12 Mar 2009 18:39:37 -0500 Received: by yw-out-2324.google.com with SMTP id 9so1181708ywe.83 for ; Thu, 12 Mar 2009 16:39:32 -0700 (PDT) Received: by 10.143.19.16 with SMTP id w16mr252227wfi.343.1236901171808; Thu, 12 Mar 2009 16:39:31 -0700 (PDT) Received: from 64-71-7-205.static.wiline.com (64-71-7-205.static.wiline.com [64.71.7.205]) by mx.google.com with ESMTPS id 30sm2538659wfd.35.2009.03.12.16.39.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 12 Mar 2009 16:39:30 -0700 (PDT) Message-ID: <49B99D30.2060803@gravitonic.com> Date: Thu, 12 Mar 2009 16:39:28 -0700 User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: Christian Schneider CC: Lukas Kahwe Smith , PHP internals References: <497A4138.2000707@gravitonic.com> <7f3ed2c30901231537j35d3b4c2i945de77a6a14dba0@mail.gmail.com> <497A578B.4080208@gravitonic.com> <3959E78B-13FC-437E-86BE-5B9EAF575BD0@pooteeweet.org> <497DA729.8070206@cschneid.com> In-Reply-To: <497DA729.8070206@cschneid.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Reserved namespaces From: andrei@gravitonic.com (Andrei Zmievski) Christian Schneider wrote: > Things gettings reserved at a later stage (like originally keywords, now > namespaces) can lead to a big deal of frustration. Therefore I think it > is crucial to have a clear naming guide now. > > And these guidelines have to be noticed by everybody who starts to use > namespaces so they have to be placed prominently. > Personally I'd even prefer them to be enforced in code so they can't be > missed. > > Removing restrictions later on causes less trouble so I wouldn't mind > too much if a couple of namespaces (or namespace prefixes) are reserved > but never used. Just a gentle reminder to make sure we don't miss this.. -Andrei