Well i'm not in favour of the importing of everything , i don't see the need for it personally but others do, as you well know. I was just trying to find a way to achieve everyone goals without sacrificing speed or correctness for those who want it =)
Shame about the single file thing though. I'm out of ideas, so best of luck :) Andrew On 7/25/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Is this something that you would consider for PHP ? > As far as I can tell from the list the two main considerations are not > pushing the decision to the executor and it being simple. I can consider it as much as I want - and applications like Zend Framework do work this way - but I also know not everybody works this way. In fact, I get requests right here for having all code of whole library handled as single file... > The only downside is that this now requires a 1 class / file. This > IMHO isn't a massive problem as long as it can be explained, and those > who have the task of splitting this up now can do an import Foo::*; ? I don't see any imports involving * happening, since they all have a common problem - you don't know what you are importing. Fortunately, they also are completely unnecessary - if you need all things inside Foo, why won't you just refer to them as Foo::things? -- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
