On 7/12/07, Stanislav Malyshev <stas@[...].com>  wrote:
>  > 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.
> 
>  My opinion is that sometimes language *should* "get in the way" - if the
>  developer is trying to do a wrong thing. Doing things right should be
>  easy, doing things wrong should be hard. I agree that this means we
>  should choose some definitions for right and wrong, and not everybody
>  would necessarily agree, but I think the benefit of the clearer program
>  structure exceeds the disadvantage of not being able to do some tricks.
>  That's one of the reasons why PHP doesn't have some things that other
>  languages might have, such as nested classes, multiple inheritance or
>  closures.
>  --
>  Stanislav Malyshev, Zend Software Architect
>  stas@[...].com   http://www.zend.com/
>  (408)253-8829   MSN: stas@[...].com
> 
>  --
>  PHP Internals - PHP Runtime Development Mailing List
>  To unsubscribe, visit: http://www.php.net/unsub.php
> 
> 


Since everyone has different opinions, we could throw off a vote and
see what the voice of the community ends up in (A tie? :O)


-- 
David Coallier,
Founder & Software Architect,
Agora Production (http://agoraproduction.com)
51.42.06.70.18

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