mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-07 15:22:31 +01:00
Code Issues Packages Projects Releases Wiki Activity

Minor wording changes from feedback.

Browse Source 
Author:halw
Date:2011-05-23T12:28:34.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@910 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2011-05-23 12:28:34 +00:00
parent 0dee10b57a
commit e07189d1b6
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/scoop-implementation.wiki
View File

@@ -8,7 +8,7 @@ The implementation of SCOOP within EiffelStudio varies from the definition as it
Some of the differences stem from the reality that SCOOP systems could be optimized for performance, including maximizing concurrency. For example, even though the SCOOP rules state that a separate call to a query is synchronous, i. e., the calling processor waits until the query completes before proceeding, if a static analysis can show that the wait is not necessary to the proper functioning of the remainder of the calling routine, then the call to the query can be done asynchronously.
In other ways, the EiffelStudio implementation may not measure up to the full SCOOP definition. Certain elements that are defined in the SCOOP descriptions may not yet be present, or only partially implemented in the EiffelStudio implementation.
In other ways, particularly for early versions, the EiffelStudio implementation may not cover all the goals of SCOOP as declared in the various publications. Certain elements that are defined in the SCOOP descriptions may not yet be present, or only partially implemented in the EiffelStudio implementation.
The differences between the EiffelStudio implementation of SCOOP and current and previous definitions of the SCOOP model are shown below.