From f4d4203f78c99284f269c3e219e5878c7d0c01f2 Mon Sep 17 00:00:00 2001 From: halw Date: Thu, 18 Jun 2009 14:43:48 +0000 Subject: [PATCH] Author:halw Date:2009-06-18T14:42:48.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@247 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../creating-new-void-safe-project.wiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/current/method/void-safe-programming-eiffel/creating-new-void-safe-project.wiki b/documentation/current/method/void-safe-programming-eiffel/creating-new-void-safe-project.wiki index 4ec77f13..0d00626c 100644 --- a/documentation/current/method/void-safe-programming-eiffel/creating-new-void-safe-project.wiki +++ b/documentation/current/method/void-safe-programming-eiffel/creating-new-void-safe-project.wiki @@ -76,7 +76,7 @@ In the introduction to the attached syntax, we used an example which showed how is a CAP for x ... but that's only true if x is a local variable or a formal argument to the routine that contains the code. -So access a detachable attribute safely, we could declare a local variable, make an assignment, and test for Void as above. Something like this: +So to access a detachable attribute safely, we could declare a local variable, make an assignment, and test for Void as above. Something like this: my_detachable_attribute: detachable MY_TYPE