Hello Gregory,
Friday, November 7, 2008, 10:14:50 PM, you wrote:
> Hi,
> Stas and company decided that they wanted namespaces to have two legal
> syntax choices:
> 1) single namespace per file:
> namespace foo;
> ...
?>>
> 2) multiple namespaces per file:
> namespace foo1 {
> }
> namespace
Steph Fox wrote:
> Hey Greg,
>
>> Remember, the patch I'm proposing would only be necessary for people
>> using un-namespaced code combined with namespaced code (already a bad
>> idea) *and* scattering "use" statements throughout the global code.
>
> If it's 'already a bad idea', why support it?
Hey Greg,
Remember, the patch I'm proposing would only be necessary for people
using un-namespaced code combined with namespaced code (already a bad
idea) *and* scattering "use" statements throughout the global code.
If it's 'already a bad idea', why support it?
Also, the *only* supported us
Hi,
Ok so I had a quick chat with greg and reread his proposal and it's actually
a sound proposal.
My original concern was that if we don't implement proper subset of
"namespace scopes" we'll have difficulty extending PHP in the future to
support function-local use declarations etc.
Howev
Hey there!
Why don't you try an implementation as:
> namespace foo;
(contents xyz)
>
namespace foob;
>
(contents xyz of as second called namespace)
>
Wouldn't it be easier to make such an application tree instead of using the
normal bracket-like opening?
Your,
--
(c) Kenan Sulayman
Freelance D
Stan Vassilev | FM wrote:
> // global, scope 1
>
> namespace { // global, scope 2 }
>
> // global, scope 1
>
> namespace { // global, scope 3 }
>
> // global, scope 1
>
> namespace foo\bar { // foo\bar, scope 4 }
>
> // global, scope 1
> ?>
I am afraid I must shed my generally congenial pu
Sorry for the second email, I just forgot to mention something regarding how
use statements apply from global scope to namespace x {}.
The best way regarding realworld usage and existing state of the art would
be to take into account the use statements in the scope above and apply the
use stat
Technically, you could argue that blah::hi() should resolve to
blah\blah::hi(), but it is very difficult to track and figure out what
"blah" means by eye. Thus, in the patch I implemented, if bracketed
namespace declarations exist, global use statements are not allowed, but
must exist within na
Hi,
Stas and company decided that they wanted namespaces to have two legal
syntax choices:
1) single namespace per file:
2) multiple namespaces per file:
I've implemented these two syntax options in a patch found at
http://pear.php.net/~greg/bracketed.patch.txt based on earlier work of
Dmit
