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

Author:halw

Browse Source 
Date:2011-07-18T18:32:24.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@945 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2011-07-21 16:35:54 +00:00
parent 38835bf7b3
commit c3420c0f79
2 changed files with 21 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/current/method/void-safe-programming-eiffel/creating-new-void-safe-project.wiki
View File

@@ -95,7 +95,7 @@ Upon creation, each element of the array will reference the same object; an obje
==Using the ''attribute'' keyword carefully==
The keyword <code>attribute</code> should be used with some care. You might be tempted to think that it would be convenient or add an extra element of safety to use self-initializing attributes widely. And in a way, you would be correct. But you should also understand that there is a price to pay for using self-initializing attributes and stable attributes. It is that upon every access, an evaluation of the state of the attribute must be made. So, as a general rule, you should avoid using self-initializing attributes only for the purpose of lazy initialization.
The keyword <code>attribute</code> should be used with some care. You might be tempted to think that it would be convenient or add an extra element of safety to use [[Void-safety: Background, definition, and tools#Self-initializing attributes|self-initializing attributes]] widely. And in a way, you would be correct. But you should also understand that there is a price to pay for using self-initializing attributes and stable attributes. It is that upon every access, an evaluation of the state of the attribute must be made. So, as a general rule, you should avoid using self-initializing attributes only for the purpose of lazy initialization.
==More about the ''attached syntax''==

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

@@ -93,9 +93,18 @@ To construct equivalent objects of type <code>STRING</code> from those of type <
<code>
non_separate_string (a_sep_str: separate STRING): STRING
-- Non-separate copy of `a_sep_str'
local
i: INTEGER
do
create Result.make_empty
across (1 |..| a_sep_str.count) as ic loop Result.append_character (a_sep_str [ic.item]) end
from
i := 1
until
i > a_sep_str.count
loop
Result.append_character (a_sep_str [i])
i := i + 1
end
end
</code>
@@ -110,8 +119,17 @@ The other alternate is to create a procedure that will print an object of type <
<code>
print_separate_string (a_sep_str: separate STRING)
-- Print `a_sep_str' on standard output.
local
i: INTEGER
do
across (1 |..| a_sep_str.count) as ic loop io.put_character (a_sep_str [ic.item]) end
from
i := 1
until
i > a_sep_str.count
loop
io.put_character (a_sep_str [i])
i := i + 1
end
end
</code>
@@ -122,9 +140,6 @@ Then you could use that procedure to output <code>my_separate_string</code>:
</code>
{{note|If you use the above solutions verbatim, you may have to set the Syntax setting to Provisional in your project settings to enable the iteration form of the loop construct. }}
=Implementation dependent behavior=