-----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 [EMAIL PROTECTED] +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----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
