Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26105
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ilisys.com.au from 203.202.10.154 cause and error)
Message-ID: <45385952.7040400@ilisys.com.au>
Date: Fri, 20 Oct 2006 13:06:26 +0800
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Christian Stocker <christian.stocker@bitflux.ch>
CC: Lukas Kahwe Smith <lsmith@php.net>,  internals@lists.php.net
References: <18.FF.27040.69DE7354@pb1.pair.com> <453857D8.3020704@bitflux.ch>
In-Reply-To: <453857D8.3020704@bitflux.ch>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] a last plead
From: glenn.richmond@ilisys.com.au (Glenn Richmond)

Hmm, this is interesting - I just joined the mailing list, but I can
relate to this. I've come across a piece of code in that has the
following line in a function within a class:

return $this;

It seems to cause an over-allocation of memory and ultimately a seg
fault in both 5.1.4 and 5.2rc4, but works in 5.04. Is this the sort of
this that you're referring to?

Glenn.

Christian Stocker wrote:
> On 19.10.2006 23:26 Uhr, Lukas Kahwe Smith wrote:
>   
>> Hi,
>>
>> I just want to say once again that all hell is going to break loose once
>> we release 5.2.0 as stable thanks to the various fatal errors we are
>> adding for perfectly working code that breaks OO theory.
>>
>> Now is the time to fix this before RC6.
>>     
>
> +1 too here.
>
> It will IMHO slow down the adoption of 5.2, as - I assume - a
> significant part of scripts will fatal out in 5.2. And this certainly
> won't make all those people happy, who already had to rewrite their
> programs for making them 5.0/1 compatible
>
> chregu
>