Re: Static and non-static methods
| From: | Andi Gutmans | Date: | Sat, 05 Apr 2003 13:32:13 +0000 |
| Subject: | Re: Static and non-static methods | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-721@lists.php.net to get a copy of this message | ||
At 03:29 PM 4/5/2003 +0200, Marcus Börger wrote:
At 14:52 05.04.2003, Andi Gutmans wrote:Let's leave this to the documentation team. We should encourage the use of "static" for static methods. AndiAt 01:12 PM 4/5/2003 +0200, Marcus Börger wrote:Agreed, breaking BC for this sounds like a bad idea to me.At 18:07 04.04.2003, Andrei Zmievski wrote:Well its a BC nightmare, and I don't really see any big advantage.On Fri, 04 Apr 2003, Derick Rethans wrote:I know :-) The reason not only i want to break BC here is to prevent users from shooting in their knees and blaming php for the erors in bug-reports later.Marcus, You and all the rest who want to break BC on this issue are welcome to use static in your code. IMO, nothing prevents you from writing nice OO code. It's not as if this is forcing you not to use static.<vent> sometimes I just hate BC.. </vent>Sometimes as in this case BC means sticking to "it's not a bug it's a feature". In PHP 4 oo was nothing more than structures with a not thought out possibility to attach normal functions. Since we now seem to reach a very good oo level, why shouldn't we remove such crap? I mean every code that uses oo will be rewritten anyway.