Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25799
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=WH8amQriL+nJ+XkgTsYEPk1N+ICF/OWMgQsFJLjfJn7dVTzr7exVxJM7h+tuSF8vxJo8cclJjUX16h3NKy7pmB1JTNWTUJlVpTWJzOywECixKeVHr3gHcgouxEIDd159PeGbMK/7Vr9fOj0NadytH7T/bwFNp9UjUzTwA5Hszi4=; c=nofws; d=albumltd.co.nz; q=dns; s=ks1
Message-ID: <45139BEE.20204@albumltd.co.nz>
Date: Fri, 22 Sep 2006 20:16:46 +1200
Organization: Album Limited
User-Agent: Thunderbird 1.5.0.5 (X11/20060719)
MIME-Version: 1.0
To: Derick Rethans <derick@php.net>
CC: Michael Wallner <mike@php.net>,  internals@lists.php.net
References: <A6.E3.49133.499A2154@pb1.pair.com> <Pine.LNX.4.62.0609221005100.3563@localhost>
In-Reply-To: <Pine.LNX.4.62.0609221005100.3563@localhost>
OpenPGP: id=0A3ABF58
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] (was: Parameter checking in 5.2)
From: jasper@albumltd.co.nz (Jasper Bryant-Greene)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Derick Rethans wrote:
> It's not necessarily a *strict* OO implementaiton though, it's one that 
> is correct. Strictness is where we would disallow setting object 
> properties on the fly while not declaring that. I would actually like to 
> see that throwing an e_strict too as that would make debugging easier as 
> well. however, in the case of signatures you *have* to be strict ... but 
> 
> I guess we would only see the full implications if you're very well 
> versed with OO theory (definitely not saying that I am).

Are we not missing the fact that static methods (at least in PHP) are
effectively bound to the specific class that they are defined on, no
matter which they are called on? f.x. see any of the multitude of posts
to this list regarding PHP's lack of late static binding.

On this note, given that there are no real inheritance rules applying
w.r.t. static methods, does it not make sense to allow different
parameters on subclasses as these are effectively different methods as
opposed to overloading in the strict sense?

- --
Jasper Bryant-Greene
Director
Album Limited

jasper@album.co.nz
+64 21 708 334 / 0800 425 286
http://www.album.co.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5-ecc0.1.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iFcDBQFFE5vtnqZ4vwo6v1gRCiekAP0cof6jTPdqcizYle2fzSAPDjucrxDMkreY
NgaS4i4hMgEAhvii80Zy6dogEFarPU9teL8zrZcyWZvIa5h+UOfrEZo=
=wcz6
-----END PGP SIGNATURE-----