Re: RfC: rethink OO inheritance strictness

From: Date: Mon, 07 Aug 2006 18:29:09 +0000
Subject: Re: RfC: rethink OO inheritance strictness
References: 1 2 3 4 5 6 7 8 9 10 11 12  Groups: php.internals 
Request: Send a blank email to internals+get-25238@lists.php.net to get a copy of this message
On Mon, August 7, 2006 8:25 am, Jeff Moore wrote: > On Aug 4, 2006, at 3:23 AM, Derick Rethans wrote: > >> - Add a new flag to methods (at the implementation level) that will >> allow to flag them as 'strict' > > Would exposing this flag to the user at method level get a bit verbose > for those who want to use it? Perhaps a class level flag for all > methods? Wasn't that proposed earlier? Its a long thread to follow, > forgive me if I've missed something. strict class blah blah blah { } as shorthand for: class blah blah blah { [strict function (){}]* } doesn't seem like it would be too terribly difficult to implement or understand... Though 'strict' may not be the right keyword... method_signature_match is a bit too verbose, though :-) sigmatch ??? 'strict' just has too many other potential meanings... -- Like Music? http://l-i-e.com/artists.htm

« previous php.internals (#25238) next »