On Wed, 11 Jul 2007 21:31:34 -0700
stas@[...].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 l
anguage concern. I'd also venture that many of the languages that enforce a file structure d
o 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 contain
ing any given class. (There's also nothing stopping them from skipping the autoloader alltog
ether.)

Similarly, allowing multiple namespaces per file does not limit the developer in any way. No
t allowing them does. I always thought a language should be designed to empower it's develop
ers, not get in their way.

-- 
Andrew Minerd
Software Architect
The Selling Source, Inc.

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php