Re: RfC: rethink OO inheritance strictness

Pierre wrote:

Hello, On 8/3/06, Derick Rethans <derick@php.net> wrote: In this particular case I think it should be possible to mark

certain internal

methods as strict and keep userspace methods loose.

But I would like to see atleast an e_strict warning of signatures are violated to give atleast the options to be strict and get warnings for it. I am pretty sure Edin doesn't give a **** about e_strict warnings... so that will work fine. I think that Zeev suggested something like this.

For what I understand (and agree), he meant the other way 'round. Users who like strictness will have to use an extra keyword in the declaration. Users who don't care will not have to change anything in their (working) code.

I'm not all that keen on a new keyword for this. How about using an interface to indicate strictness? Isn't this really what interfaces are all about? -Rasmus