[PHP-DEV] Re: One more critical problem in 5.4
Just to make everything clear, I'm not sure if it was my mistake change 5_4 branch, but currently 5_4 branch (after 322964 commit) solves the header problem. Thanks for the work. On Tue, 31 Jan 2012 10:04:34 +0200, yoram bar haim wrote: Sorry, problem is not solved yet. I committed a possible fix to trunk. It's pretty much along the patch from you, I just hat to fix crashes in the cli server and need to do some more testing before merging into PHP_5_4. Thank you for your reports! Mike -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: One more critical problem in 5.4
On Tue, 2012-01-31 at 03:58 -0500, Michael Wallner wrote: On Tue, 31 Jan 2012 10:04:34 +0200, yoram bar haim wrote: Sorry, problem is not solved yet. I committed a possible fix to trunk. It's pretty much along the patch from you, I just hat to fix crashes in the cli server and need to do some more testing before merging into PHP_5_4. Hi Mike, According to my testing revision 322931 and 322964 fix the issue on the 5.4 branch. I also tested that display_startup_errors=1 doesn't make apache to crash (as this was the original report). Thanks for the fixes (: Kaplan -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: One more critical problem in 5.4
On Wed, Feb 1, 2012 at 10:57 AM, Lior Kaplan lio...@zend.com wrote: On Tue, 2012-01-31 at 03:58 -0500, Michael Wallner wrote: On Tue, 31 Jan 2012 10:04:34 +0200, yoram bar haim wrote: Sorry, problem is not solved yet. I committed a possible fix to trunk. It's pretty much along the patch from you, I just hat to fix crashes in the cli server and need to do some more testing before merging into PHP_5_4. Hi Mike, According to my testing revision 322931 and 322964 fix the issue on the 5.4 branch. I also tested that display_startup_errors=1 doesn't make apache to crash (as this was the original report). Thanks for the fixes (: Kaplan Seems like the last blocking bug for RC7 has been fixed :) Stas : planning an RC7 release ? Thx all for your great work ^^ Julien -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Uploading 5.4 RC to unstable (Was: Upcoming transition of php5 to 5.4)
Hi, I was thinking that it could be a good idea (after current version migrates to testing) to upload 5.4RCx to unstable to begin work on transition as soon as possible. RC releases should have stable API(?), so application wise there's no problem. I'll fill a release critical bug in our BTS, so the 5.4 version don't migrate to testing and close it with stable 5.4.0 release. Ccing PHP internals to let them know and ask if it is a good idea (the 5.4RC will be probably used by more people when uploaded to Debian unstable, i.e. it means more testing, but also more bugreports). O. -- Forwarded message -- From: Ondřej Surý ond...@sury.org Date: Wed, Feb 1, 2012 at 08:40 Subject: Upcoming transition of php5 to 5.4 To: Debian Release debian-rele...@lists.debian.org Hi, this is just a heads up that we would like to ship wheezy with php5 5.4 which is in upstream RC phase now (and in debian-experimental). It introduce a couple of incompatible changes (for a full list see attached UPGRADING file), most notably (not listing minor changes and added features): - default charset is now utf-8 - magic_quotes are deprecated (with warning) - safe_mode and register_globals was removed - three new reserved words: callable, insteadof and trait - multibyte support is now default - removed syntax (break $var, continue $var) - sqlite(1) extension was removed (already done in php5.3 in Debian) I am inclined to let the current php5 in unstable to transition to testing and then upload next 5.4.0 RC to unstable with transition blocking bug, so we can start testing existing software as soon as possible. I also plan to provide official backports for Debian squeeze, so people can come and test new php5.4 before they upgrade to wheezy. Final note: We already had similar transitions in php (4-5, 5.2-5.3, etc.), so it's not really a big deal, but it will require some amount of work hence this email. Ondrej P.S.: Please Cc: me as I am not subscribed to the list (but I do check the web archives). -- Ondřej Surý ond...@sury.org -- Ondřej Surý ond...@sury.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: One more critical problem in 5.4
On Wed, 01 Feb 2012 11:57:08 +0200, Lior Kaplan wrote: On Tue, 2012-01-31 at 03:58 -0500, Michael Wallner wrote: On Tue, 31 Jan 2012 10:04:34 +0200, yoram bar haim wrote: Sorry, problem is not solved yet. I committed a possible fix to trunk. It's pretty much along the patch from you, I just hat to fix crashes in the cli server and need to do some more testing before merging into PHP_5_4. Hi Mike, According to my testing revision 322931 and 322964 fix the issue on the 5.4 branch. I also tested that display_startup_errors=1 doesn't make apache to crash (as this was the original report). Thanks for the fixes (: Thank you all for your reports and sorry to Stats David that the output layer caused another unplanned RC. Regards, Mike -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Uploading 5.4 RC to unstable (Was: Upcoming transition of php5 to 5.4)
Hi Ondřej, I'd wait for RC7 in any case, and with some luck it will be the final RC for 5.4.0. With my Debian hat on, I would wait for the official release, as to minimize the noise we'll get in Debian from testing RCs. The recent RCs all had some major issues fixed/changed in them (which is better to test with dedicated people than the general users of Debian). Kaplan On Wed, 2012-02-01 at 11:11 +0100, Ondřej Surý wrote: Hi, I was thinking that it could be a good idea (after current version migrates to testing) to upload 5.4RCx to unstable to begin work on transition as soon as possible. RC releases should have stable API(?), so application wise there's no problem. I'll fill a release critical bug in our BTS, so the 5.4 version don't migrate to testing and close it with stable 5.4.0 release. Ccing PHP internals to let them know and ask if it is a good idea (the 5.4RC will be probably used by more people when uploaded to Debian unstable, i.e. it means more testing, but also more bugreports). O. -- Forwarded message -- From: Ondřej Surý ond...@sury.org Date: Wed, Feb 1, 2012 at 08:40 Subject: Upcoming transition of php5 to 5.4 To: Debian Release debian-rele...@lists.debian.org Hi, this is just a heads up that we would like to ship wheezy with php5 5.4 which is in upstream RC phase now (and in debian-experimental). It introduce a couple of incompatible changes (for a full list see attached UPGRADING file), most notably (not listing minor changes and added features): - default charset is now utf-8 - magic_quotes are deprecated (with warning) - safe_mode and register_globals was removed - three new reserved words: callable, insteadof and trait - multibyte support is now default - removed syntax (break $var, continue $var) - sqlite(1) extension was removed (already done in php5.3 in Debian) I am inclined to let the current php5 in unstable to transition to testing and then upload next 5.4.0 RC to unstable with transition blocking bug, so we can start testing existing software as soon as possible. I also plan to provide official backports for Debian squeeze, so people can come and test new php5.4 before they upgrade to wheezy. Final note: We already had similar transitions in php (4-5, 5.2-5.3, etc.), so it's not really a big deal, but it will require some amount of work hence this email. Ondrej P.S.: Please Cc: me as I am not subscribed to the list (but I do check the web archives). -- Ondřej Surý ond...@sury.org -- Ondřej Surý ond...@sury.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Uploading 5.4 RC to unstable (Was: Upcoming transition of php5 to 5.4)
On Wed, 1 Feb 2012, Ondřej Surý wrote: Ccing PHP internals to let them know and ask if it is a good idea (the 5.4RC will be probably used by more people when uploaded to Debian unstable, i.e. it means more testing, but also more bugreports). Sounds like a good idea to me. This is why we have RCs (and you guys have unstable IIRC). Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Uploading 5.4 RC to unstable (Was: Upcoming transition of php5 to 5.4)
hi, On Wed, Feb 1, 2012 at 12:24 PM, Lior Kaplan lio...@zend.com wrote: Hi Ondřej, I'd wait for RC7 in any case, and with some luck it will be the final RC for 5.4.0. With my Debian hat on, I would wait for the official release, as to minimize the noise we'll get in Debian from testing RCs. The recent RCs all had some major issues fixed/changed in them (which is better to test with dedicated people than the general users of Debian). I'd to disagree. All these issues were not new (as in not coming from post RC commits) and have been discovered by general users. So yes, hell yeah!, generate useful noises so we can be sure to release an outstanding 5.4.0 Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [php-maint] Uploading 5.4 RC to unstable (Was: Upcoming transition of php5 to 5.4)
On 02/01/2012 06:11 PM, Ondřej Surý wrote: Hi, I was thinking that it could be a good idea (after current version migrates to testing) to upload 5.4RCx to unstable to begin work on transition as soon as possible. RC releases should have stable API(?), so application wise there's no problem. I'll fill a release critical bug in our BTS, so the 5.4 version don't migrate to testing and close it with stable 5.4.0 release. Ccing PHP internals to let them know and ask if it is a good idea (the 5.4RC will be probably used by more people when uploaded to Debian unstable, i.e. it means more testing, but also more bugreports). O. I support this. Removal of some legacy features, like these functions: session_is_registered(), session_register() and session_unregister(), or removal of .ini stuff like register_globals and register_long_arrays WILL break applications. The sooner we have PHP 5.4 in SID, the sooner people will realize issues, and start fixing. Anyways, I think we should write few words in -devel@, including mentioning the above feature removal (or maybe simply showing the URL: http://www.php.net/releases/NEWS_5_4_0_alpha1.txt, but I don't think that's enough, insisting on session_register() removal for example, which must be still widely used, is crucial). Also, I'd like to know. In PHP 5.3, we had few deprecated functions (ereg / eregi pops to mind, but also return new as reference). Are these now totally removed from PHP 5.4, or do they still show with deprecation warnings? Thoughts? Thomas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] SVN Account Request: szarkos
Working with Pierre Joye on the build hosts (for Windows), automated testing and test infrastructure for PHP/Windows. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4 Benchmarks
Hi, As many of you know we made huge improvements in PHP 5.4 memory usage (enabling higher concurrency) and runtime performance. We've done our own benchmarks but it'd be great to hear from others re: what you're seeing with your real-world apps. If you have any experiences to share please do. Benchmarking is not easy and can be misleading (config not being the same, compiler options, different version of byte code caches, etc..) so the more data points we get the better the info re: performance gains. Thanks, Andi
Re: [PHP-DEV] PHP 5.4 Benchmarks
hi Andi, We do automatic perf tests as part of the CI. Some of the results can be seen here for example here: http://windows.php.net/downloads/snaps/ostc/pftt/perf/results-20120119-5.3.9-5.4.0RC6.html for a 5.3.9 vs 5.4.0RC6 comparison. There are other in the same location. We are going to do add some more perf related tests later. Cheers, On Wed, Feb 1, 2012 at 7:08 PM, Andi Gutmans a...@zend.com wrote: Hi, As many of you know we made huge improvements in PHP 5.4 memory usage (enabling higher concurrency) and runtime performance. We've done our own benchmarks but it'd be great to hear from others re: what you're seeing with your real-world apps. If you have any experiences to share please do. Benchmarking is not easy and can be misleading (config not being the same, compiler options, different version of byte code caches, etc..) so the more data points we get the better the info re: performance gains. Thanks, Andi -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] PHP 5.4 Benchmarks
Cache results are of course important. Memory usage would be great too. Thanks!! Andi -Original Message- From: Pierre Joye [mailto:pierre@gmail.com] Sent: Wednesday, February 01, 2012 10:19 AM To: Andi Gutmans Cc: internals@lists.php.net Subject: Re: [PHP-DEV] PHP 5.4 Benchmarks hi Andi, We do automatic perf tests as part of the CI. Some of the results can be seen here for example here: http://windows.php.net/downloads/snaps/ostc/pftt/perf/results-20120119- 5.3.9-5.4.0RC6.html for a 5.3.9 vs 5.4.0RC6 comparison. There are other in the same location. We are going to do add some more perf related tests later. Cheers, On Wed, Feb 1, 2012 at 7:08 PM, Andi Gutmans a...@zend.com wrote: Hi, As many of you know we made huge improvements in PHP 5.4 memory usage (enabling higher concurrency) and runtime performance. We've done our own benchmarks but it'd be great to hear from others re: what you're seeing with your real-world apps. If you have any experiences to share please do. Benchmarking is not easy and can be misleading (config not being the same, compiler options, different version of byte code caches, etc..) so the more data points we get the better the info re: performance gains. Thanks, Andi -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 5.4 Benchmarks
hi! I could add zend optimizer to the stack but we do not have a license (or is it free for the optimizer only?). APC should join the party soon, not sure yet if it is ready yet. We will run compat tests first. About the memory usage, yes, this is on my todos. I have a tool for that (on win) which has less than 1% impact on perf so we can compare all in one run. But that will have to wait post final. Cheers, On Wed, Feb 1, 2012 at 7:24 PM, Andi Gutmans a...@zend.com wrote: Cache results are of course important. Memory usage would be great too. Thanks!! Andi -Original Message- From: Pierre Joye [mailto:pierre@gmail.com] Sent: Wednesday, February 01, 2012 10:19 AM To: Andi Gutmans Cc: internals@lists.php.net Subject: Re: [PHP-DEV] PHP 5.4 Benchmarks hi Andi, We do automatic perf tests as part of the CI. Some of the results can be seen here for example here: http://windows.php.net/downloads/snaps/ostc/pftt/perf/results-20120119- 5.3.9-5.4.0RC6.html for a 5.3.9 vs 5.4.0RC6 comparison. There are other in the same location. We are going to do add some more perf related tests later. Cheers, On Wed, Feb 1, 2012 at 7:08 PM, Andi Gutmans a...@zend.com wrote: Hi, As many of you know we made huge improvements in PHP 5.4 memory usage (enabling higher concurrency) and runtime performance. We've done our own benchmarks but it'd be great to hear from others re: what you're seeing with your real-world apps. If you have any experiences to share please do. Benchmarking is not easy and can be misleading (config not being the same, compiler options, different version of byte code caches, etc..) so the more data points we get the better the info re: performance gains. Thanks, Andi -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] PHP 5.4 Benchmarks
Optimizer+ is free and packaged in Zend Server Community Edition. Happy to get you and anyone else who wants to run benchmarks a copy out of cycle. We haven't put a preview up yet but have it working. Re: memory usage, I've seen some great results so definitely will be nice to see what others are seeing. Thanks, Andi -Original Message- From: Pierre Joye [mailto:pierre@gmail.com] Sent: Wednesday, February 01, 2012 10:37 AM To: Andi Gutmans Cc: internals@lists.php.net Subject: Re: [PHP-DEV] PHP 5.4 Benchmarks hi! I could add zend optimizer to the stack but we do not have a license (or is it free for the optimizer only?). APC should join the party soon, not sure yet if it is ready yet. We will run compat tests first. About the memory usage, yes, this is on my todos. I have a tool for that (on win) which has less than 1% impact on perf so we can compare all in one run. But that will have to wait post final. Cheers, On Wed, Feb 1, 2012 at 7:24 PM, Andi Gutmans a...@zend.com wrote: Cache results are of course important. Memory usage would be great too. Thanks!! Andi -Original Message- From: Pierre Joye [mailto:pierre@gmail.com] Sent: Wednesday, February 01, 2012 10:19 AM To: Andi Gutmans Cc: internals@lists.php.net Subject: Re: [PHP-DEV] PHP 5.4 Benchmarks hi Andi, We do automatic perf tests as part of the CI. Some of the results can be seen here for example here: http://windows.php.net/downloads/snaps/ostc/pftt/perf/results- 20120119 - 5.3.9-5.4.0RC6.html for a 5.3.9 vs 5.4.0RC6 comparison. There are other in the same location. We are going to do add some more perf related tests later. Cheers, On Wed, Feb 1, 2012 at 7:08 PM, Andi Gutmans a...@zend.com wrote: Hi, As many of you know we made huge improvements in PHP 5.4 memory usage (enabling higher concurrency) and runtime performance. We've done our own benchmarks but it'd be great to hear from others re: what you're seeing with your real-world apps. If you have any experiences to share please do. Benchmarking is not easy and can be misleading (config not being the same, compiler options, different version of byte code caches, etc..) so the more data points we get the better the info re: performance gains. Thanks, Andi -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 5.4 Benchmarks
On Wed, 2012-02-01 at 18:08 +, Andi Gutmans wrote: We've done our own benchmarks but it'd be great to hear from others Can we also hear from you? :-) johannes who doesn't have proper benchmarks himself, but is interested in seeing them ;-) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 5.4 Benchmarks
APC should join the party soon, not sure yet if it is ready yet. We will run compat tests first. I ran into a crashing blocker with APC on 5.4: https://bugs.php.net/bug.php?id=60845 If anyone has the bandwidth to look into that, I'd love to help out in any way I can. (Sorry for the thread hijack…) S
RE: [PHP-DEV] PHP 5.4 Benchmarks
Absolutely. Will gather those and send them over... Andi -Original Message- From: Johannes Schlüter [mailto:johan...@schlueters.de] Sent: Wednesday, February 01, 2012 10:49 AM To: Andi Gutmans Cc: internals@lists.php.net Subject: Re: [PHP-DEV] PHP 5.4 Benchmarks On Wed, 2012-02-01 at 18:08 +, Andi Gutmans wrote: We've done our own benchmarks but it'd be great to hear from others Can we also hear from you? :-) johannes who doesn't have proper benchmarks himself, but is interested in seeing them ;-)
[PHP-DEV] Property Accessors Type Hinting
Type Hinting was not in the original RFC, is type hinting stable enough to be
included with the Property Accessors functionality or is there no clear
agreement made with them yet?
https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented?#read-only_and_write-only_properties
Could be:
?php
class TimePeriod {
public array $Hours {
...
}
}
?
