Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33910
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.235 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=J4KRWn3I6kzqvg7S3Ru5gPFhFAxBYRrRoasa1m8Y9Ywg5G1auMubLHtLHBm9fD+PQp6JvXD/RuYHaEHY8Amo+R8hrjire+VG3dhdEMpgo6dW2zMPZmo6ThVURDP/Bhy4WPfrS/yQ1quoiX7M+5QGI5sp1ZqXPD3ptCLzoypGUug=
Message-ID: <52dbac0f0712101159r3a27843bya005c5b43b1ef97e@mail.gmail.com>
Date: Mon, 10 Dec 2007 16:59:27 -0300
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <52dbac0f0712101053k31b06733u6bbc9d3d38806a8a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_19412_15430560.1197316767154"
References: <52dbac0f0712100837m76aeb9b1o8f2ff666451a73a9@mail.gmail.com>
	 <475D78D4.6050509@zend.com>
	 <52dbac0f0712101053k31b06733u6bbc9d3d38806a8a@mail.gmail.com>
Subject: Re: [PHP-DEV] RFC: Arguments (and suggestions) against the current implementation of namespaces
From: malterisio777@gmail.com ("Martin Alterisio")

------=_Part_19412_15430560.1197316767154
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

2007/12/10, Martin Alterisio <malterisio777@gmail.com>:
>
>
> > c) If bracketed namespaces are a no-go, consider the possibility of
> > > declaring the full name of the namespaced element in its definition:
> >
> > Which would lead to people routinely mixing different namespaces inside
> > one file. Bad idea. Also would kill namespaced functions and constants,
> > which would make organizing libraries using those impossible.
>
>
> Why would it lead to people routinely mixing different namespaces inside
> one file?
> Why is this bad in the first place?
> Why is it the language the one to decide which is the better way to
> organize code?
>
> Also, that would not kill neither namespaced functions nor constants:
>
> <?php
> function namespaced::foo() {
> ...
> }
> const namespaced::CONST = "I'm namespaced!";
> ?>


PS: An example of an organization model that wouldn't be possible with the
current implementation of namespaces:

Imagine that I'm writing a small module for my app. Just a main class, some
helper classes and exceptions. For the purposes of this module I just find
more organized to keep everything in a one file. Also, I expect exceptions
only to be raised in most exceptional cases, therefore I see that is best to
keep them in a subordinated but different namespace. I have two namespaces,
e.g.: MyModule and MyModule:Exceptions, but I can't keep them in the same
file. I don't see the point on having the exceptions in a different file,
and I really prefer to keep the main namespace of my module as clean as
possible. The language just took away the possibility to decide which
organization schema I prefer.

------=_Part_19412_15430560.1197316767154--