From 7b268a23dd26b8ba503b1825e30816c98e2fb9d2 Mon Sep 17 00:00:00 2001 From: jfiat Date: Wed, 18 Feb 2015 10:21:52 +0000 Subject: [PATCH] Fix wrong link to the "once key" mechanism. Issue reported at https://docs.google.com/spreadsheet/ccc?key=0At9HXU58N0BAdFNpbUljRHRjR2NqYk9feXd1V0Zubmc&usp=sharing (commit by Conaclos) git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1414 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../creating-new-void-safe-project.wiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/current/eiffel/Language_reference/void-safe-programming-eiffel/creating-new-void-safe-project.wiki b/documentation/current/eiffel/Language_reference/void-safe-programming-eiffel/creating-new-void-safe-project.wiki index 972b630a..57e9e2e7 100644 --- a/documentation/current/eiffel/Language_reference/void-safe-programming-eiffel/creating-new-void-safe-project.wiki +++ b/documentation/current/eiffel/Language_reference/void-safe-programming-eiffel/creating-new-void-safe-project.wiki @@ -167,7 +167,7 @@ So in this simple form, attached x can be used instead of x / There is a code pattern for functions that exists in some Eiffel software to effect "once-per-object / lazy evaluation". -{{note|As of EiffelStudio version 6.6, the use of this code pattern effecting "once per object" is no longer necessary. V6.6 includes explicit support for once routines which can be adjusted by a [[ET: Other Mechanisms#Adjusting once semantics with "once keys"|once key]] to specify once per object.}} +{{note|As of EiffelStudio version 6.6, the use of this code pattern effecting "once per object" is no longer necessary. V6.6 includes explicit support for once routines which can be adjusted by a [[ET: Once routines and shared objects#Adjusting once semantics with "once keys"|once key]] to specify once per object.}} This "once-per-object" code pattern employs a cached value for some object which is not exported. When it is applied, the "once-per-object" function checks the attachment status of the cached value. If the cached value is void, then it is created and assigned to Result. If the cached value was found already to exist, then it is just assigned to Result.