> De : Dmitry Stogov [mailto:dmi...@zend.com] > > I think we should just repeat the related D semantic. > It must be defined in contracts inheritance rules. > > What if we have contracts for prototype method in parent class and > interface? > Should we still validate contracts of parent and interface if we add our > owns? > etc.
I would prefer contract inheritance to follow a logic more similar to what we use for PHP constructors/destructors (parent method is executed only if explicitely called). 'require(@parent)', for example, would mean 'check parent pre-conditions !'. The same for every constraint type. This is not exactly the D way but is is more consistent with the PHP way. And there's no real reason to follow D there. Not sure we should authorize constraints in interfaces, at least for a first version. Cheers François -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
