mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-07 15:22:31 +01:00
de27c5b184
Date:2011-05-14T20:46:11.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@895 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
26 lines
1.2 KiB
Plaintext
26 lines
1.2 KiB
Plaintext
[[Property:title|SCOOP practical matters]]
|
|
[[Property:weight|-1]]
|
|
[[Property:uuid|87f78898-2bbb-b134-0128-e55401a61a05]]
|
|
{{UnderConstruction}}
|
|
|
|
|
|
=Introduction=
|
|
|
|
''SCOOP practical matters'' is a collection of advice for using SCOOP effectively. Here you will find practical information that supplements the rules and definitions of the basic [[Concurrent Eiffel with SCOOP|SCOOP model]], or that is unique to the implementation of SCOOP in EiffelStudio.
|
|
|
|
=SCOOP project settings=
|
|
|
|
SCOOP adds only a single keyword to the Eiffel language: <code>separate</code>. In single- (or mono-) threaded Eiffel, the <code>separate</code> keyword is ignored, and the SCOOP-specific validity rules are not applied.
|
|
|
|
In order to make SCOOP processing possible, you must enable the proper project settings. Actually, there's really just one mandatory setting: '''Concurrency''', and the value you need is '''SCOOP''', as shown in the section of the Project Settings dialog below. Still, in addition to the Concurrency project setting, remember that it is recommended that for new projects you use enable [[Creating a new void-safe project#Project settings for void-safe projects|the settings that guarantee void-safety]].
|
|
|
|
|
|
|
|
[[Image: SCOOP project setting]]
|
|
|
|
|
|
|
|
|
|
|
|
|