Re: 4.0.7 when?
| From: | Zeev Suraski | Date: | Tue, 16 Oct 2001 15:04:47 +0000 |
| Subject: | Re: 4.0.7 when? | ||
| References: | 1 2 3 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-68050@lists.php.net to get a copy of this message | ||
At 16:34 16-10-01, Edin Kadribasic wrote:
At 15:22 16-10-01, Yasuo Ohgaki wrote:This bug is really problematic, because effectively, it's not a bug. Prior to the current CVS, PHP behaved pretty inconsistently with function redefinitions. This caused all sorts of issues, as can be seen in bug 9884. Sometime since 4.0.6, I changed the behavior to be consistent - if a function is redefined during compile-time, it will complain, period. Unfortunately, this obviously has a negative side effect, and a fairly big one, too. Code that used to work, if ($foo) {I hope "critical bug" include segfault at the end of "./php -q run-tests.php". (Posted to php-qa)IMHO no, it doesn't, as it appears to be related to your 'extreme' configuration, and not something in the plain simple PHP :) We need to figure out which extension causes it before we can really dive in... IMHO the only really critical bug is #13616. I cannot really test the RC since the application that I use the most (SquirrelMail for example) do not work.
return;} ...function definitions... no longer works. Instead, you have to do something like: if (!$foo): ...function definitions... endif; Fixing this is trivial, it means reverting the fix for bug 9884. The question is whether we do that or not, and we need to decide about it... Zeev