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

Author:halw

Browse Source 
Date:2009-06-10T15:49:51.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@232 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-06-10 15:49:51 +00:00
parent b4cb3277f0
commit d2f0deebf5
2 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
documentation/current/method/void-safe-programming-eiffel/converting-existing-software-void-safety/index.wiki
View File

@@ -28,6 +28,9 @@ So in the discussion below, you will see references to these classes:
|}
It's not important that you know much about the details of these classes. We will, however, look at certain parts of the classes in enough detail to resolve the conversion issues.
=Conversion considerations=
==To redesign or not to redesign==

2
documentation/current/method/void-safe-programming-eiffel/void-safety-background-definition-and-tools.wiki
View File

@@ -178,7 +178,7 @@ So, self-initializing attributes are just ordinary attributes, and they can be
end
</code>
In the example above, the attribute <code>value</code> will be attached to an object of type STRING, in fact, the empty string, if no other initialization occurs before the first access of <code>value</code>.
In the example above, the attribute <code>value</code> will be attached to an object of type <code>STRING</code>, in fact, the empty string, if no other initialization occurs before the first access of <code>value</code>.
===Rule for conformance===