Just for the record, most compilers have such "bugs". It happens when the
compiler is too lenient and allows incorrect code to be compiled. I've seen
similar things happen in C/C++ and other languages.
At 09:20 PM 7/12/2005 +0200, Pierre-Alain Joye wrote:
On Tue, 12 Jul 2005 20:53:16 +0200 (CEST)
[EMAIL PROTECTED] (Derick Rethans) wrote:
> On Tue, 12 Jul 2005, Chuck Hagenbuch wrote:
>
> > Relax, I'm not debating the decision. Just:
> >
> > PLEASE can someone put a big fat warning on the php 4.4
> > announcement on www.php.net that it breaks existing code?
> >
> > I already have people upgrading to it and wondering why they
> > get tons of warnings now. We're fixing them as quick as we can,
> > but honestly, given that PHP never gave us a notice about them
> > before, there are going to be a lot, and a lot in old releases
> > too. It'd be helpful if on the php side people were at least
> > given a chance not to shoot themselves in the foot.
>
> They were already shooting them in the foot by using references
> wrong... and you did have about a month to test your code (Horde
> I presume) with the new PHP 4.4 release candidates. And it's just
> a notice... which you should always have off on a production
> machine. So I don't think we should put a BIG warning on php.net
> because people didn't quite understand how references worked (me
> included).
The bug #33643 is not what I can call "shooting in my own foot".
There were cases were I fully agree to break BC, but this one and
its pairs, not. I agree that it's nice to solve this problem, my
point here is we fix a Zend bug by removing some facilities in the
langage. I only hope that we will allow that again in future
versions.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
