Updated wikipage Converting EiffelVision 2 Systems to Void-Safety. (Signed-off-by:roc_admin).

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

documentation/24.05/eiffel/Coding_Standards/Eiffel-Code-Comments.wiki

@@ -1,4 +1,4 @@
-[[Property:modification_date|Mon, 13 Dec 2021 12:42:51 GMT]]
+[[Property:modification_date|Thu, 27 Jun 2024 10:45:27 GMT]]
 [[Property:publication_date|Thu, 03 Jan 2019 18:00:43 GMT]]
 [[Property:uuid|146E241E-C367-4F16-9CCE-6F11E5F7860A]]
 [[Property:weight|1]]
@@ -145,11 +145,12 @@ f (a_arg: INTEGER): BOOLEAN
 
 This will have exactly the same effect as using <e>-- <Precursor></e> when <e>f</e> is made effective/redefined from a single parent. However, when making effective/redefining from multiple parents, then comments will come from the parent class declaration in <e>BASE</e>.
 
-Again, because precursor comments do not affect compilation, they are not checked at compile time. Specifying an incorrect class will yield a warning message in [[EiffelStudio]]'s code browsing tools, to the effect:
+Again, because precursor comments do not affect compilation, they are not checked at compile time. Specifying an incorrect class will yield a warning message in [/doc/eiffelstudio/EiffelStudio EiffelStudio]'s code browsing tools, to the effect:
 
 <e>
 -- Unable to retrieve the comments from redefinition of {CLASS_NAME}.
 </e>
 
 === Library Documentation Generation ===
-Precursor comments are supported in all code browsing/documentation facilities, whether it be the integrated [[Contract Viewer]], the [[Feature Relation Tool]] or the Eiffel documentation generation facilities. Using <e>-- <Precursor></e> will ensure the comments are brought up from a parent declaration.
+Precursor comments are supported in all code browsing/documentation facilities, whether it be the integrated [/doc/eiffelstudio/Contract_Editor_tool Contract Viewer
+], the [https://www.eiffel.org/doc/eiffelstudio/Feature_views Feature Relation Tool] or the Eiffel documentation generation facilities. Using <e>-- <Precursor></e> will ensure the comments are brought up from a parent declaration.

documentation/24.05/solutions/gui-building/eiffelvision-2/Vison2_howto/converting-eiffelvision-2-systems-void-safety.wiki

@@ -1,9 +1,11 @@
+[[Property:modification_date|Thu, 27 Jun 2024 10:51:45 GMT]]
+[[Property:publication_date|Thu, 27 Jun 2024 10:51:45 GMT]]
 [[Property:title|Converting EiffelVision 2 Systems to Void-Safety]]
 [[Property:weight|1]]
 [[Property:uuid|96e01318-700b-da6e-42d1-14fee219daf5]]
 ==Introduction==
 
-In order to convert systems that employ EiffelVision 2 (Vision2) to [[Void-safe Programming in Eiffel|void-safety]], some adjustments may be needed depending on its usage.  This page describes the various usage scenarios of Vision2 that will need to be converted in order to adhere to void-safety.
+In order to convert systems that employ EiffelVision 2 (Vision2) to [[Void-safe programming in Eiffel|void-safety]], some adjustments may be needed depending on its usage.  This page describes the various usage scenarios of Vision2 that will need to be converted in order to adhere to void-safety.
 <!--break-->
 ==Inheritance Purely from an Interface Class==
 
@@ -82,5 +84,5 @@ The following steps are needed during the conversion:
 * Remove <eiffel>`make'</eiffel>, rename <eiffel>`initialize'</eiffel> to <eiffel>`make'</eiffel>, and make sure that any calls to Precursor do not override any settings set in <eiffel>`initialize'</eiffel>.  The ordering may need to be changed in order to make the code void-safe.  See <eiffel>EV_POPUP_WINDOW_IMP.make</eiffel> (Windows implementation) where the setting of <eiffel>`user_can_resize'</eiffel> is performed after the Precursor call so that is doesn't get overriden.
 
 
-{{SeeAlso|[[Void-Safe Programming in Eiffel]]}}
+{{SeeAlso|[[Void-safe programming in Eiffel]]}}