Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26106
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain albumltd.co.nz from 210.55.31.88 cause and error)
DomainKey-Status: bad (key type)
DomainKey-Signature: a=rsa-sha1; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:OpenPGP:Content-Type:Content-Transfer-Encoding; b=BYNIplsQ2TJ+VERAmpH9vaPzQp9mu51f+eKZLSfVH8IMBdLYjB2kno0wtdV2U7Prev5RJVi8xMm46a3LFiUDc+eEcck6/X3O/JdPrzjkp8gHSBAYfcey9GMC9hlNOzkRF71cj261JpG7DzXmAvXITpNvvbBjR9v0mlstoQhf51k=; c=nofws; d=albumltd.co.nz; q=dns; s=ks1
Message-ID: <45386AB4.60504@albumltd.co.nz>
Date: Fri, 20 Oct 2006 19:20:36 +1300
Organization: Album Limited
User-Agent: Thunderbird 1.5.0.7 (X11/20060909)
MIME-Version: 1.0
To: Glenn Richmond <glenn.richmond@ilisys.com.au>
CC: Christian Stocker <christian.stocker@bitflux.ch>, 
 Lukas Kahwe Smith <lsmith@php.net>,
  internals@lists.php.net
References: <18.FF.27040.69DE7354@pb1.pair.com> <453857D8.3020704@bitflux.ch> <45385952.7040400@ilisys.com.au>
In-Reply-To: <45385952.7040400@ilisys.com.au>
OpenPGP: id=0A3ABF58
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] a last plead
From: jasper@albumltd.co.nz (Jasper Bryant-Greene)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Glenn,

'return $this' is perfectly acceptable and indeed very common code. It
works fine for me in 5.1.4 - you might like to report a bug if you can
reproduce a segfault...

What is being referred to here is things like 'abstract static'
functions that are completely meaningless from a theoretical point of
view (static functions are bound to the class they are defined on and do
not have inheritance rules so how can they be abstract?) but are still
being used by some people.

The argument is that we should not unnecessarily break these people's
code just because it makes no sense. Personally, I don't buy into this
argument. Perhaps if their code breaks and there is a good explanation
in the error message, they might start writing OO code that isn't
nonsensical.

Jasper


Glenn Richmond wrote:
> 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
>>   
> 

- --
Jasper Bryant-Greene
Director
Album Limited

jasper@albumltd.co.nz
+64 21 708 334 / 0800 425 286
http://www.albumltd.co.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5-ecc0.1.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iFcDBQFFOGq0nqZ4vwo6v1gRCv93AP40IC/FslI+O6BvPvSWwqQ8KzfJdZCoNxaW
Qufw5UC2NQEAmbXhhotg72ht80f1t0sL8SWiPfonq6zAFDwSNdi7Mnc=
=lMPv
-----END PGP SIGNATURE-----