Re: [PHP-DEV] Internals read-only (was: Re: [PHP-DEV] namespace improvements to be committed very soon - final review)

Jani, if your blood pressure raises when reading "normal people's" messages because your dictatorial mind cannot stand the opinion of people that you regard inferior to yourself, my suggestion would be to either go see a shrink or quit this open source project. Here's hoping you will be abl

Re: [PHP-DEV] Internals read-only (was: Re: [PHP-DEV] namespace improvements to be committed very soon - final review)

On Thu, 2007-12-13 at 08:55 -0500, Marco Tabini wrote: > I am just a lurker, so take this with the due grain of salt, but > simply making internals@ read-only is just going to drive people to > contact the core team members directly (thus likely *increasing* your > blood pressure :-)). I thin

Re: [PHP-DEV] Internals read-only (was: Re: [PHP-DEV] namespace improvements to be committed very soon - final review)

On 13-Dec-07, at 8:08 AM, Jani Taskinen wrote: On Thu, 2007-12-13 at 10:00 +0100, Derick Rethans wrote: To to get back to the point of the noise on the lists - it's getting out of hand, and I am afraid that if we don't solve this any time soon, the lists will be useless for any sort of dec

[PHP-DEV] Internals read-only (was: Re: [PHP-DEV] namespace improvements to be committed very soon - final review)

On Thu, 2007-12-13 at 10:00 +0100, Derick Rethans wrote: > To to get back to the point of the noise on the lists - it's getting out > of hand, and I am afraid that if we don't solve this any time soon, the > lists will be useless for any sort of decent discussion and promoting > even more secret

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

On Wed, 12 Dec 2007, Stanislav Malyshev wrote: > > because it's impossible to discuss anything on internals without the > > noise coming from "outside"..? Could we finally make this list > > read-only for every one but the @php.net people? I get enough spam > > already, spam from this list is n

Re: [PHP-DEV] namespace improvements to be committed very soon -final review

hello! Jani Taskinen wrote: Nice to hear some work is done but I get very annoyed every time I see the words "behind the scenes" (or something alike). I guess it was because it's impossible to discuss anything on internals without the noise coming from "outside"..? Could we finally make this lis

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

Nice to hear some work is done but I get very annoyed every time I see the words "behind the scenes" (or something alike). I guess it was It is much more efficient to communicate in person (preferably physically, but can be phone, IM, chat, etc.) than to write semi-anonymous mails to public li

Re: [PHP-DEV] namespace improvements to be committed very soon -final review

Jani Taskinen wrote: > Nice to hear some work is done but I get very annoyed every time I see > the words "behind the scenes" (or something alike). I guess it was > because it's impossible to discuss anything on internals without the > noise coming from "outside"..? Could we finally make this list

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

On Tue, 2007-12-11 at 22:33 -0600, Gregory Beaver wrote: > Any brackets adds another set of shift/reduce to the parser, regardless > of how the syntax of the language is defined. That's not all with that syntax. Leads to a delayed declaration which is done at run-time, not at compile-time - th

Re: [PHP-DEV] namespace improvements to be committed very soon -final review

On 12/12/2007, Nathan Rixham <[EMAIL PROTECTED]> wrote: > > if their income depends on it, hmm, I wonder, why the hell are they > > only complaining? > point well made > > > always been open and we have always gladly given account to > > people who contributed. > and it's been well noticed, not

Re: [PHP-DEV] namespace improvements to be committed very soon -final review

> if their income depends on it, hmm, I wonder, why the hell are they > only complaining? point well made > always been open and we have always gladly given account to > people who contributed. and it's been well noticed, not to mention the amount of times you have to repeat yourself. Particular

Re: [PHP-DEV] namespace improvements to be committed very soon -final review

Hello Nathan, if their income depends on it, hmm, I wonder, why the hell are they only complaining? The amount of people being constructive and not actual developers with a php.net account is close to zero. That is what Jani had in mind. We have always been open and we have always gladly given a

Re: [PHP-DEV] namespace improvements to be committed very soon -final review

Surely the noise coming from outside are people's valid opinions? I mean it's the people making the noise who have to live with decisions made on the internals list, on a daily basis, and for most there income depends on it. It's not just php you're discussing, it's thousands of developers wo

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

Nice to hear some work is done but I get very annoyed every time I see the words "behind the scenes" (or something alike). I guess it was because it's impossible to discuss anything on internals without the noise coming from "outside"..? Could we finally make this list read-only for every one but t

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

Ken Stanley wrote: > > > On Dec 11, 2007 6:13 PM, Gregory Beaver <[EMAIL PROTECTED] > > wrote: > > The example above shows that imported names are reset at each > namespace > declaration. There is no prohibition on this code: > > namespace one; { >

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

On Dec 11, 2007 6:13 PM, Gregory Beaver <[EMAIL PROTECTED]> wrote: > The example above shows that imported names are reset at each namespace > declaration. There is no prohibition on this code: > > namespace one; { > use Blah::A; > // code > } > namespace two; { > use Foo::A; > // code > } > ?>

Re: [PHP-DEV] namespace improvements to be committed very soon -final review

Sam Barrow wrote: > Is this patch going to be implemented in the PHP release? yes, these are patches against cvs.php.net php5 -r PHP_5_3 and HEAD Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

Is this patch going to be implemented in the PHP release? On Tue, 2007-12-11 at 18:42 -0500, David Coallier wrote: > On Dec 11, 2007 6:13 PM, Gregory Beaver <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I've been furiously working behind the scenes with Stas and Dmitry, and > > have some enhancements

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

On Dec 11, 2007 6:42 PM, David Coallier <[EMAIL PROTECTED]> wrote: > On Dec 11, 2007 6:13 PM, Gregory Beaver <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I've been furiously working behind the scenes with Stas and Dmitry, and > > have some enhancements to namespaces in the form of 2 patches. > > > >

Re: [PHP-DEV] namespace improvements to be committed very soon - final review

On Dec 11, 2007 6:13 PM, Gregory Beaver <[EMAIL PROTECTED]> wrote: > Hi, > > I've been furiously working behind the scenes with Stas and Dmitry, and > have some enhancements to namespaces in the form of 2 patches. > > 1) multiple namespaces per file > 2) use ::name; > > 1) multiple namespaces per f

[PHP-DEV] namespace improvements to be committed very soon - final review

Hi, I've been furiously working behind the scenes with Stas and Dmitry, and have some enhancements to namespaces in the form of 2 patches. 1) multiple namespaces per file 2) use ::name; 1) multiple namespaces per file This is implemented as such: The example above shows that imported names a