Apo4, when introducing POST, mentions that there is a corresponding "PRE" block "for design-by-contract programmers".
However, I see the POST block being used as a finalize; and thus allowing (encouraging?) it to have side effects. I can't help feeling that contract/assertion checking should not have side effects. Furthermore, there should be options to turn off PRE/POST processing for higher performance. Perhaps we'll learn more about contracts (inc. invariants, inheritance) in a later apo? Will we still use the Class::Contract module? Dave. -- Dave Whipp, Senior Verification Engineer, Fast-Chip inc., 950 Kifer Rd, Sunnyvale, CA. 94086 tel: 408 523 8071; http://www.fast-chip.com Opinions my own; statements of fact may be in error.
