Author:halw

Date:2010-01-05T21:46:20.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@384 abb3cda0-5349-4a8f-a601-0c33ac3a8c38

documentation/current/eiffelstudio/_images/AutoTest_filter_drop_down.png.data

@@ -0,0 +1,3 @@
+title=AutoTest filter drop down
+author=halw
+path=content/autotest-filter-drop-down

documentation/current/eiffelstudio/_images/AutoTest_filter_result.png.data

@@ -0,0 +1,3 @@
+title=AutoTest filter result
+author=halw
+path=content/autotest-filter-result

documentation/current/eiffelstudio/_images/AutoTest_filter_result_fail.png.data

@@ -0,0 +1,3 @@
+title=AutoTest filter result fail
+author=halw
+path=content/autotest-filter-result-fail

documentation/current/solutions/concurrent-computing/eiffelthread/eiffelthread-tutorial/once-features-multithreaded-mode.wiki

@@ -13,7 +13,7 @@ Then the once feature is not initialized once per process but once per thread. Y
 
 Current once features in Eiffel are once per thread. This means that when a once feature is called in a thread, the Eiffel run-time will check whether it has been already computed in this thread. If not, the once feature will be initialized and computed. This seems to be a relevant way of managing once features in multithreaded mode: most of the time, a once called in a thread is not likely to share its result. 
 
-However, in some case, we need to share once features. 
+However, in some cases, we need to share once features. 
 
 Moreover, an Eiffel programmer should be able to have an alternative between a once per thread or per process implementation.