NICE Eiffel Standards Group -- Library Committee Mailing List To post to list: NICE-ESG-Libs@atlanta.twr.com To send mail to the Chairman of the committee: NICE-ESG-Libs-chair@atlanta.twr.com Administrative matters (sign up, unsubscribe, mail problems, etc): NICE-ESG-Libs-request@atlanta.twr.com
Date: Tue, 12 Dec 95 15:13:31 EST From: tynor (Steve Tynor) Subject: `is_equal' postcondition To: NICE-ESG-Libs@atlanta.twr.com I prefer Bertrand's solution. In Roger's case, nothing is checked at runtime (the assertion is strictly a comment), whereas in Bertrand's, at least the bounds can be checked. Also, I may be being dense, but what does Roger mean by: | entirety. However, when the non-executable part is commented out, | the remaining subexpression does not yield a meaningful result when | evaluated. When the non-executable part is commented out, the remaining result is a subset of the postcondition's promise. It's meaningful, just not the whole story. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Programming needn't be like penance or oat bran. Steve Tynor Internet: Steve.Tynor@atlanta.twr.com Tower Technology WWW: http://www.twr.com/
Date: Tue, 12 Dec 95 21:28:15 GMT From: bertrand@eiffel.fr (Bertrand Meyer @ SOL) Subject: Correction To: NICE-ESG-Libs@atlanta.twr.com Sorry, one line did not make sense. I should have proofread my message. Replace Making the whole assertion into the postcondition is overkill. by Making the whole assertion become a comment is overkill. I apologize for any confusion. -- BM
