Re: Simple Namespace Proposal
| From: | Andrew Minerd | Date: | Thu, 12 Jul 2007 20:53:23 +0000 |
| Subject: | Re: Simple Namespace Proposal | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-30870@lists.php.net to get a copy of this message | ||
On Wed, 11 Jul 2007 21:31:34 -0700
stas@zend.com (Stanislav Malyshev) wrote:
> I understand we're forcing some structure here, but I think
> actually it's good - and many other languages have it either
> by design or de-facto.
Personally, I'm of the opinion that file structure should be an application concern, not a
language concern. I'd also venture that many of the languages that enforce a file structure do
so because they include a packaging system; PHP doesn't.
> And in fact we started doing it in php 5 with autoloading and
> classname->filename paradigm.
Not really. There's nothing to stop someone from lumping multiple classes into a single file
AND using an autoloader, provided they have a scheme for locating the specific file containing any
given class. (There's also nothing stopping them from skipping the autoloader alltogether.)
Similarly, allowing multiple namespaces per file does not limit the developer in any way. Not
allowing them does. I always thought a language should be designed to empower it's developers,
not get in their way.
--
Andrew Minerd
Software Architect
The Selling Source, Inc.