mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-06 23:02:28 +01:00
Update wikipage SCOOP implementation. (Signed-off-by:bmeyer).
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1927 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -1,13 +1,9 @@
|
||||
[[Property:title|SCOOP implementation]]
|
||||
[[Property:weight|9]]
|
||||
[[Property:uuid|eeb07907-e036-f3d6-5297-a7c44cfd1900]]
|
||||
The implementation of SCOOP within EiffelStudio varies from the definition as it has been presented in publications during the model's evolution.
|
||||
|
||||
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, particularly for early versions, the EiffelStudio implementation may not cover all the goals of SCOOP as stated 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.
|
||||
The implementation of SCOOP is the result of many years of design and refinement of the model. This page describes specific properties of its current state, in particular ways in which it differs from some of the earlier publications about the model.
|
||||
|
||||
|
||||
=Known limitations=
|
||||
|
||||
Reference in New Issue
Block a user