Re^5: Programming is combat

DBC is integral to Perl 6

Since the subject's come up ;-)

PRE and POST will obviously handle pre-/post-conditions for methods. However - I've not spotted an easy way of expressing class invariants. Is there something that I've missed?

Also, there do not appear be a built ins for dealing with naming conflicts as there are in languages like Eiffel. How would I rename method foo() to bar() in a sub-class and keep the pre- and post-conditions?

Disclaimer: I've still not read A12 properly, so apologies if the answer is in there and I missed it when I skimmed it :-)

Comment on Re^5: Programming is combat Select or Download Code

Replies are listed 'Best First'.
Re^6: Programming is combat by TimToady (Parson) on Jul 09, 2004 at 21:19 UTC
It should be possible to do class invariants one way or another. Perhaps we could just say that any PRE and POST properties on the class itself automagically get attached to any methods defined in the class. As for naming conflicts, A12 does talk about that some in the context of Roles, but similar reasoning applies to inherited methods. In general, renaming violates Liskov substitutability, so we discourage (but do not prevent) that approach in favor of distinguishing via multiple dispatch where possible, and use of a switch method where not. But in cases where renaming is used, it'll be important to make sure the correct PRE and POST are called at each level. If renaming is done simply by a wrapper method in the derived class, this will happen automatically, I suspect. Nonetheless, if you're changing the contract of a class, you probably ought to consider delegation instead of inheritance. And the delegation mechanism certainly has plenty of hooks for renaming.	[reply]

Replies are listed 'Best First'.

Re^6: Programming is combat
by TimToady (Parson) on Jul 09, 2004 at 21:19 UTC

As for naming conflicts, A12 does talk about that some in the context of Roles, but similar reasoning applies to inherited methods. In general, renaming violates Liskov substitutability, so we discourage (but do not prevent) that approach in favor of distinguishing via multiple dispatch where possible, and use of a switch method where not. But in cases where renaming is used, it'll be important to make sure the correct PRE and POST are called at each level. If renaming is done simply by a wrapper method in the derived class, this will happen automatically, I suspect.

Nonetheless, if you're changing the contract of a class, you probably ought to consider delegation instead of inheritance. And the delegation mechanism certainly has plenty of hooks for renaming.

[reply]