From fca4485745c75664620c98b8c78406ff530abb7e Mon Sep 17 00:00:00 2001 From: eiffel-org Date: Sat, 19 Jan 2019 20:11:49 +0000 Subject: [PATCH] Updated wikipage Concurrency. (Signed-off-by:bmeyer). git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@2136 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- documentation/18.11/solutions/concurrent-computing/index.wiki | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/documentation/18.11/solutions/concurrent-computing/index.wiki b/documentation/18.11/solutions/concurrent-computing/index.wiki index 48f2e776..683c4751 100644 --- a/documentation/18.11/solutions/concurrent-computing/index.wiki +++ b/documentation/18.11/solutions/concurrent-computing/index.wiki @@ -1,4 +1,4 @@ -[[Property:modification_date|Tue, 20 Nov 2018 12:44:24 GMT]] +[[Property:modification_date|Sat, 19 Jan 2019 20:11:49 GMT]] [[Property:publication_date|Tue, 20 Nov 2018 12:44:24 GMT]] [[Property:link_title|Concurrency]] [[Property:title|Concurrency]] @@ -18,6 +18,7 @@ In most programming languages, the way to obtain threaded applications is to rel Thread libraries are at a lower level of abstraction than modern programming languages, requiring you to manage the interaction of threads manually through such techniques as mutual exclusion semaphores. Eiffel offers a higher-level mechanism: [[SCOOP]] (Simple Concurrent Object-Oriented Programming), which greatly simplifies the writing of concurrent applications and avoids many of the typical pitfalls of concurrency such as "data races". SCOOP is the recommended approach to concurrent Eiffel programming. For details see: +* [[SCOOP_tutorial|SCOOP tutorial (hands-on)]]: build a small concurrent email system, step by step. * The [[SCOOP|SCOOP documentation]] for the recommended approach to concurrent programming in Eiffel. * The [[EiffelThreads|EiffelThreads documentation]] if you need to exert fine control on the execution and synchronization of threads.