Re: [PHP-DEV] trunk is alive and open

2010/4/29 Andi Gutmans : >> -Original Message- >> From: Johannes Schlüter [mailto:johan...@schlueters.de] >> Sent: Tuesday, April 27, 2010 9:40 AM >> To: Pierre Joye >> Cc: Gwynne Raskind; Ilia Alshanetsky; Kalle Sommer Nielsen; Lukas Kahwe >> Smith; Andi Gutmans; Derick Rethans; PHP Develo

Re: [PHP-DEV] trunk is alive and open

Am 29.04.2010 07:28, schrieb Andi Gutmans: > I think with traits, performance enhancements and a few additional > changes we already have a pretty substantial version. +1 -- Sebastian BergmannCo-Founder and Principal Consultant http://sebastian-bergmann.de/

Re: [PHP-DEV] trunk is alive and open

As I've mentioned in the past I think we are better off with shorter release cycles and less features per cycle. Reduces risk and enables us to push out value faster. For example, we have made (and are still making) significant performance enhancements to the runtime. It'd be a shame if that waite

RE: [PHP-DEV] trunk is alive and open

> -Original Message- > From: Johannes Schlüter [mailto:johan...@schlueters.de] > Sent: Tuesday, April 27, 2010 9:40 AM > To: Pierre Joye > Cc: Gwynne Raskind; Ilia Alshanetsky; Kalle Sommer Nielsen; Lukas Kahwe > Smith; Andi Gutmans; Derick Rethans; PHP Developers Mailing List > Subject: Re

Re: [PHP-DEV] backslash, really ... ?

Sylvain Rabot wrote: On Wed, 2010-04-28 at 15:29 -0700, Chad Fulton wrote: You can take a look at the RFP if you like. It discusses the pros and cons of various possible separators, and why they chose the backslash. http://wiki.php.net/rfc/namespaceseparator Thanks.

Re: [PHP-DEV] backslash, really ... ?

On Thu, 2010-04-29 at 00:44 +0200, Jérôme Loyet wrote: > 2010/4/29 Sylvain Rabot : > > On Wed, 2010-04-28 at 15:29 -0700, Chad Fulton wrote: > >> You can take a look at the RFP if you like. It discusses the pros and cons > >> of various possible separators, and why they chose the backslash. > >> >

Re: [PHP-DEV] backslash, really ... ?

2010/4/29 Sylvain Rabot : > On Wed, 2010-04-28 at 15:29 -0700, Chad Fulton wrote: >> You can take a look at the RFP if you like. It discusses the pros and cons >> of various possible separators, and why they chose the backslash. >> >> http://wiki.php.net/rfc/namespaceseparator > > Thanks. > >> >> <

Re: [PHP-DEV] backslash, really ... ?

On Wed, 2010-04-28 at 15:29 -0700, Chad Fulton wrote: > You can take a look at the RFP if you like. It discusses the pros and cons > of various possible separators, and why they chose the backslash. > > http://wiki.php.net/rfc/namespaceseparator Thanks. > >

Re: [PHP-DEV] backslash, really ... ?

You can take a look at the RFP if you like. It discusses the pros and cons of various possible separators, and why they chose the backslash. http://wiki.php.net/rfc/namespaceseparator I've been using namespaces for a few months now with the backslash sy

Re: [PHP-DEV] backslash, really ... ?

On Wed, 2010-04-28 at 16:58 -0500, Matt Wilson wrote: > So, you decided to jump in to criticize a design decision that went in after > several months of discussion, without any insight into why it was done the > way it was? > Not really criticizing, maybe a bit, but more expressing my disappoin

Re: [PHP-DEV] backslash, really ... ?

So, you decided to jump in to criticize a design decision that went in after several months of discussion, without any insight into why it was done the way it was? On Apr 28, 2010, at 4:45 PM, Sylvain Rabot wrote: > Hi, > > The comment I'm about to make is behind the times, and, now, useless,

[PHP-DEV] backslash, really ... ?

Hi, The comment I'm about to make is behind the times, and, now, useless, I know, but I can't hold me. You chose for the namespace feature, a great feature besides, the backslash ?? really ?? Come on guys, among all the possibilities, you have chosen, according to me, the most hideous character p

Re: [PHP-DEV] ereg deprecation?

On Apr 28, 2010, at 11:21 AM, Stan Vassilev wrote: >> Hi, >> I think I asked this before on IRC, but I've forgotten the answer. I was >> just remembering that the ereg extension was due to be deprecated in PHP6 - >> does this still apply to trunk? > > Deprecated since 5.3, and was to be remove

Re: [PHP-DEV] ereg deprecation?

Hi, I think I asked this before on IRC, but I've forgotten the answer. I was just remembering that the ereg extension was due to be deprecated in PHP6 - does this still apply to trunk? Deprecated since 5.3, and was to be removed in 6.0. In that context, it remains deprecated in all new bran

Re: [PHP-DEV] ereg deprecation?

Michael Maclean wrote: Hi, I think I asked this before on IRC, but I've forgotten the answer. I was just remembering that the ereg extension was due to be deprecated in PHP6 - does this still apply to trunk? ...and by "deprecated" I of course mean "removed". *Ahem*. (Thanks Philip!) -- Chee

[PHP-DEV] ereg deprecation?

Hi, I think I asked this before on IRC, but I've forgotten the answer. I was just remembering that the ereg extension was due to be deprecated in PHP6 - does this still apply to trunk? -- Cheers, Michael -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www

Re: [PHP-DEV] Obscure token name

On Mon, 2010-04-26 at 16:32 +0200, mathieu.suen wrote: > I am wondering why is the token name so incomprehensible ? > Like T_PAAMAYIM_NEKUDOTAYIM... I don't mind if we change the name in the error message. Seems to be an issue for some ... but I think you have to look it (quickly) up the first tim

Re: [PHP-DEV] Obscure token name

Zeev Suraski wrote: At 23:39 27/04/2010, Sufficool, Stanley wrote: The rest of PHP5 is in English, why do I have to strain my brain or fire up my browser to decipher "Unexpected token T_PAAMAYIM_NEKUDOTAYIM on line ## in ". How many native Hebrew speaking programmers will be put off by changin

RE: [PHP-DEV] Obscure token name

At 23:39 27/04/2010, Sufficool, Stanley wrote: The rest of PHP5 is in English, why do I have to strain my brain or fire up my browser to decipher "Unexpected token T_PAAMAYIM_NEKUDOTAYIM on line ## in ". How many native Hebrew speaking programmers will be put off by changing this to T_DOUBLE_CO