Re: [PHP-DEV] RFC: How PHP utilizes the Google SoC

Philip Olson wrote: On Mar 4, 2008, at 7:07 PM, Daniel Brown wrote: On Tue, Mar 4, 2008 at 5:17 PM, Philip Olson <[EMAIL PROTECTED]> wrote: The Google Summer of Code sponsors students to work on Open Source projects over each summer. This RFC introduces guidelines and goals involving how

Re: [PHP-DEV] RFC: How PHP utilizes the Google SoC

On Mar 4, 2008, at 7:07 PM, Daniel Brown wrote: On Tue, Mar 4, 2008 at 5:17 PM, Philip Olson <[EMAIL PROTECTED]> wrote: The Google Summer of Code sponsors students to work on Open Source projects over each summer. This RFC introduces guidelines and goals involving how we handle the SoC pr

Re: [PHP-DEV] RFC: How PHP utilizes the Google SoC

On Tue, Mar 4, 2008 at 5:17 PM, Philip Olson <[EMAIL PROTECTED]> wrote: > > The Google Summer of Code sponsors students to work on Open Source > projects over each summer. This RFC introduces guidelines and goals > involving how we handle the SoC process. [snip="important info"] Philip (or

Re: [PHP-DEV] Re: RFC: How PHP utilizes the Google SoC

David Coallier wrote: > Marcus was last year, he is again this year. Gotcha. Thanks for the clarification. -- Edward Z. YangGnuPG: 0x869C48DA HTML Purifier Anti-XSS Filter [[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]] -- PHP Intern

Re: [PHP-DEV] Re: RFC: How PHP utilizes the Google SoC

> Philip Olson wrote: > > The SoC Administrator is designated - hopefully before February 1. Marcus was last year, he is again this year. > > Somewhat behind the ball, are we? :o) > Nothing is behind the walls... for once :) -- David, Re-read what you are replying. -- PHP Internals - PHP

[PHP-DEV] Re: RFC: How PHP utilizes the Google SoC

Philip Olson wrote: > The SoC Administrator is designated - hopefully before February 1. Somewhat behind the ball, are we? :o) -- Edward Z. YangGnuPG: 0x869C48DA HTML Purifier Anti-XSS Filter [[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48D

[PHP-DEV] RFC: How PHP utilizes the Google SoC

The Google Summer of Code sponsors students to work on Open Source projects over each summer. This RFC introduces guidelines and goals involving how we handle the SoC process. Synopsis: - Nominate an administrator early, encourage idea development year round, and focus on nomi

[PHP-DEV] Re: Undocumented 5.3 features

Hi! - Nowdocs aren't documented http://docs.php.net/manual/en/language.types.string.php#language.types.string.syntax.nowdoc Ah, great! - .htaccess-like .ini files undocumented Heh? You mean the .htaccess FastCGI thingy? yep, that thingy. - new version constants undocumented Thos

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

On Tue, Mar 4, 2008 at 8:38 PM, Andi Gutmans <[EMAIL PROTECTED]> wrote: > Why do you say it's not documented? > http://www.aconus.com/~oyaji/www/apache_linux_php.htm > http://tinyurl.com/2o8pq2 According to the latter link, our windows binaries don't enable zend-multibyte, is this true? -Hanne

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

On Tue, Mar 4, 2008 at 8:38 PM, Andi Gutmans <[EMAIL PROTECTED]> wrote: > OK just kidding and I agree it would be nice to have it better > documented in the mainstream docs. As it applies mostly to the Asian > users though (Chinese/Japanese) who usually seek localized docs it's > probably not a

[PHP-DEV] Re: Docs for 5.3!

Hi! - Nowdocs aren't documented - .htaccess-like .ini files undocumented - [HOST=] and [PATH=] .ini sections undocumented - new version constants undocumented BTW, not sure if other things from the top of NEWS file are documented either... -- Stanislav Malyshev, Zend Software Architect [EMAI

[PHP-DEV] Undocumented 5.3 features

On Tue, Mar 4, 2008 at 8:22 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote: > I agree with the intent - documentation is *very* important. Even > though, people use undocumented features too (probably cursing the lazy > developers on the way ;) Indeed. And in few years noone has a clue wtf al

RE: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

> -Original Message- > From: Hannes Magnusson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 04, 2008 11:18 AM > To: Stas Malyshev > Cc: Antony Dovgal; Marcus Boerger; Andi Gutmans; > internals@lists.php.net > Subject: Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an > re2c [1]

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

Hi! Improving on that statement: The coolest feature ever is worth absolutely nothing unless it is documented. I agree with the intent - documentation is *very* important. Even though, people use undocumented features too (probably cursing the lazy developers on the way ;) BTW, as far as I

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

On Tue, Mar 4, 2008 at 7:28 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote: > The best idea is worth nothing for the users unless it's part of the > release. Improving on that statement: The coolest feature ever is worth absolutely nothing unless it is documented. Don't care if its a new lan

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

Hello Andi, Tuesday, March 4, 2008, 7:51:07 AM, you wrote: > Hi Marcus, Johannes, and all, > First of all let me say that I have no conceptual problem with replacing > the scanner with re2c. If it's cleaner, performs better and a better > maintained piece of software (let's hope Marcus doesn't g

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

Hi! Right. Please take more time if needed, no need to rush and release something half-working. If it takes several months to prepare 5.3 release, let it be so. With this approach we would never release 5.3 - each couple of months somebody would have a cool idea which would only require init

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

Hi! We can definitely work towards RE2C in parallel and as Stas said the engine hasn't really been changing very much recently to make this hard (we finished our todos for 5.3). We could even branch off PHP 5.4 right Small correction - we still have a couple of todo items. I think we'll have

[PHP-DEV] Copy a good idea: Ubuntu brainstorm

Hi all, As many probably have noticed, the internals mailinglist is flushed with ideas and people discussing about it. Although this is highly valuable, it makes looking through the e-mail list almost a daily task. Ubuntu QA has a nice solution for this: Ubuntu brainstorm (http://brainstorm.

RE: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

> -Original Message- > From: Marcus Boerger [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 04, 2008 1:39 AM > To: Andi Gutmans > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an > re2c [1] based lexer > > This sounds like we are going to d

Re: [PHP-DEV] PHP6 & floatval() BC issue

Hi Christian, On Tue, Mar 4, 2008 at 3:17 PM, Christian Schneider <[EMAIL PROTECTED]> wrote: > Hi all, > playing around with PHP 6 I noticed the following BC issue: > floatval("4.2foo") gives an E_NOTICE "A non well formed numeric value > encountered". The type casting (float)"4.2foo" still wor

[PHP-DEV] PHP6 & floatval() BC issue

Hi all, playing around with PHP 6 I noticed the following BC issue: floatval("4.2foo") gives an E_NOTICE "A non well formed numeric value encountered". The type casting (float)"4.2foo" still works as before. The change was introduced with the conversion of floatval() to zend_parse_parameters with

RE: [PHP-DEV] Bug #44087

> Jani is right, this is not a PHP bug. You need to configure your system > correctly to make sure the libs are checked in the right order for They are - per the bug report, the ordering is correct: # ldconfig -p | grep -i xml2 libxml2.so.2 (libc6,x86-64) => /usr/local/lib/libxml2.so.2 libxm

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

Marcus Boerger wrote: This sounds like we are going to do the same mistake over and over and over again. Who is forcing a hard time line on us? Why are we late in the develoment I don't get it at all. We haven't done all steps that were on our radar for 5.3. Now that we finally found time to add

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

On 04.03.2008 12:38, Marcus Boerger wrote: > This sounds like we are going to do the same mistake over and over and over > again. Who is forcing a hard time line on us? Why are we late in the > develoment I don't get it at all. Right. Please take more time if needed, no need to rush and release s

Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer

Hello Andi, Tuesday, March 4, 2008, 7:51:07 AM, you wrote: > Hi Marcus, Johannes, and all, > First of all let me say that I have no conceptual problem with replacing > the scanner with re2c. If it's cleaner, performs better and a better > maintained piece of software (let's hope Marcus doesn't g