Updated wikipage Design by Contract and Assertions. (Signed-off-by:roc_admin).

git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@2510 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
eiffel-org
2026-05-05 15:23:26 +00:00
parent f8ba1f48dd
commit 1b3e8e072c
@@ -1,3 +1,5 @@
[[Property:modification_date|Tue, 05 May 2026 15:23:25 GMT]]
[[Property:publication_date|Tue, 05 May 2026 15:23:25 GMT]]
[[Property:title|Design by Contract and Assertions]] [[Property:title|Design by Contract and Assertions]]
[[Property:weight|5]] [[Property:weight|5]]
[[Property:uuid|41172f82-227a-96b1-2dad-624f04374ee0]] [[Property:uuid|41172f82-227a-96b1-2dad-624f04374ee0]]
@@ -113,7 +115,7 @@ If we remove the instructions from a routine and leave its signature, header com
end end
</code> </code>
This specification of <code>set_second</code> tells us what is required of reuse consumers if they wish to use <code>set_second</code> and what <code>set_second</code> promises to do for them. Importantly, it does that without revealing how it does it does what it does. This specification of <code>set_second</code> tells us what is required of reuse consumers if they wish to use <code>set_second</code> and what <code>set_second</code> promises to do for them. Importantly, it does that without revealing how it does what it does.
So, this specification view, officially called the contract view, is how consumers of class <code>TIME_OF_DAY</code> would view the feature. So, this specification view, officially called the contract view, is how consumers of class <code>TIME_OF_DAY</code> would view the feature.