mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-09 00:02:53 +01:00
Author:admin
Date:2008-09-25T16:19:15.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@44 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -36,7 +36,7 @@ Creating a thread is like creating an Eiffel object:
|
||||
create my_thread
|
||||
</code>
|
||||
|
||||
{{note| '''Note''': You have created a thread object but have not started the thread itself yet. <br/>
|
||||
{{note|You have created a thread object but have not started the thread itself yet. <br/>
|
||||
To run the thread, use the feature <eiffel>launch</eiffel> from <eiffel>THREAD</eiffel>. }}
|
||||
<code> my_thread.launch</code>
|
||||
On the Eiffel side, the procedure <eiffel>execute</eiffel> will be launched. This procedures deferred in class <eiffel>THREAD</eiffel>, you have to define it in <eiffel>MY_THREAD</eiffel>.
|
||||
@@ -65,7 +65,7 @@ The implementation of the class <eiffel>MUTEX</eiffel> is mapped on the C standa
|
||||
<code> my_mutex.is_set</code>
|
||||
|
||||
|
||||
{{note| '''Note''': on Windows: The <eiffel>MUTEX</eiffel> objects on Windows are recursive while they are not on Unix. A recursive mutex can be locked twice by the same thread. }}
|
||||
{{note|on Windows: The <eiffel>MUTEX</eiffel> objects on Windows are recursive while they are not on Unix. A recursive mutex can be locked twice by the same thread. }}
|
||||
|
||||
{{warning| '''Caution''': be sure that a mutex is unlocked when it is disposed. }}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user