Author:halw

Date:2011-02-09T05:42:57.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@755 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2011-02-09 05:42:57 +00:00
parent 541bf3ce57
commit 4a1a7c6db2

View File

@@ -1,7 +1,6 @@
[[Property:title|Dining philosophers]] [[Property:title|Dining philosophers]]
[[Property:weight|-12]] [[Property:weight|-12]]
[[Property:uuid|569f012e-7913-fbdf-7ad7-cd17d82e64aa]] [[Property:uuid|569f012e-7913-fbdf-7ad7-cd17d82e64aa]]
{{Beta}} {{Beta}}
@@ -51,7 +50,7 @@ and you're not wearing your SCOOP glasses, this could look a little odd to you.
However, with SCOOP in mind, we realize that the fork objects are shared resources to which exclusive access must be secured before a philosopher can eat. In this example, the fork object themselves don't really do anything except serve that purpose. (Take a look at the FORK class, and you'll see that it has no features.) However, with SCOOP in mind, we realize that the fork objects are shared resources to which exclusive access must be secured before a philosopher can eat. In this example, the fork object themselves don't really do anything except serve that purpose. (Take a look at the FORK class, and you'll see that it has no features.)
In other concurrency problems, it is likely that shared resources would play a more active role than the forks of the dining philosophers, but here it's just not necessary. In real world concurrency problems, it is likely that shared resources would play a more active role than the forks of the dining philosophers, but here it's just not necessary.