Re: RfC: rethink OO inheritance strictness

Hello Michael, first of all the decision never was my decision, second i am not going to let peole run into problem hell. I coded enough PHP 4 OO to see that it didn't make any sense and caused a lot of errors in the code we wrote back then. But once again it is not my decision, i was not even my choice of OO model. The only thing i might have to excuse myself for is that i spent hundreds and hundreds of hours to get the oo code work at all and yes i know that we still have problems. Nothing more to say here, go hunt the guys that decide, not idiots devoting free time to make this all work. best regards marcus p.s.: I am not a Java fan, infact i avoid it wherever possible. Friday, July 21, 2006, 10:55:05 AM, you wrote: > Hi (Marcus), > unfortunately I'm not very happy with the direction OO strictness takes > in PHP. I'm sure I'm not alone and many people second this feeling. > Precisely, let's have a look at the following: > mike@honeybadger:~/build/php-5.2-debug$ cli -d"error_reporting=8191" -r > 'class c{function f(){}} class d extends c{function f($a){}}' > Strict Standards: Declaration of d::f() should be compatible with that of > c::f() in Command line code on line 1 > mike@honeybadger:~/build/php-unicode-debug$ cli -d"error_reporting=8191" > -r 'class c{function f(){}} class d extends c{function f($a){}}' > Fatal error: Declaration of d::f() must be compatible with that of c::f() in Command line code > on line 1 > I *really* think that this enforcements are no good idea and > I _beg_ you that we leave this "area" to interfaces. > Regards, > -- > Michael Best regards, Marcus