That might seem odd but it's not inheritance.
Yeah. And that's my main concern with it. It seems like inheritance (and is described like inheritance in the RFC at present--which is a documentation issue that will need to be addressed in the manual eventually), but it isn't. I feel it should be one or the other: either have full inheritance semantics, or have full conflict-resolution semantics like when trait methods conflict, at least by default. I think the latter is better. I'm really warming to the idea of using 'default' as I proposed in my last email, though, as essentially doing what André suggested 'in reverse'--i.e. a 'non-final' marker. Ben. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
