Hello,
On Tue, Aug 12, 2008 at 2:39 AM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> but if the {} syntax is introduced, it will be made to affect only the
>> code inside it, right? If so, I fail to see your point, since the new
>> syntax will solve that problem.
>
> While introducing a whole collection of new problems - such as that we will
> have now split scope, that you can get in and out many times in the same
> file. As we discussed on the list many times, it's not exactly what we want
> and definitely not the use case it was designed for. I don't see any use for
> it besides promoting bad coding practices.
To me
namespace A {
code
}
namespace B {
code
}
code
seems equivalent to
namespace A;
code
namespace B;
code
namespace <none>;
code
Only nicer. And I can hardly how it's going to cause more problems?
But if that's so, fine.
My point is that if we are going to allow multiple namespaces per file
solely on the perspective of permitting packaging, we should also
allow mixing namespaced and non-namespaced code for that same
perspective, and the current syntax is not going to allow that.
I'd really like the {} syntax if multiple namespaces per file is
allowed. If it's not, then it's not much more than syntactic sugar and
I couldn't care less.
> --
> Stanislav Malyshev, Zend Software Architect
> [EMAIL PROTECTED] http://www.zend.com/
> (408)253-8829 MSN: [EMAIL PROTECTED]
>
>
--
Etienne Kneuss
http://www.colder.ch
Men never do evil so completely and cheerfully as
when they do it from a religious conviction.
-- Pascal
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
