From e5cad2d741aae765c3d9f73723b2effa8be66f9c Mon Sep 17 00:00:00 2001 From: halw Date: Thu, 14 Jul 2011 18:11:44 +0000 Subject: [PATCH] Added uncontrolled precondition clauses as wait conditions, plus ref to producer-consumer example. Author:halw Date:2011-07-14T18:11:44.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@937 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../concurrent-computing/concurrent-eiffel-scoop/index.wiki | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/index.wiki b/documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/index.wiki index c3b43472..7707cc9b 100644 --- a/documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/index.wiki +++ b/documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/index.wiki @@ -247,7 +247,10 @@ Uncontrolled precondition clauses demand an adaptation of precondition semantics {{Info|A violation of a '''controlled precondition clause''' will cause an exception in the caller as soon as the violation is detected. A violation of an '''uncontrolled precondition clause''' does not result in an exception in the caller. Rather, the feature application waits to execute until such time as the precondition clause holds. }} -So, the client's responsibility is limited to those precondition clauses that are controlled. +So, the client's responsibility is limited to those precondition clauses that are controlled. Uncontrolled precondition clauses become '''wait conditions'''. + + +{{SeeAlso|The {PRODUCER}.store feature in the [[Producer-consumer|producer-consumer]] example. When called by {PRODUCER}.produce it becomes a '''wait condition'''.}} ===Postconditions===