From b383dfb6458c3871fa09ac71768899e9c1683822 Mon Sep 17 00:00:00 2001 From: acolyer Date: Wed, 28 Jul 2004 15:55:07 +0000 Subject: [PATCH] fix for Bugzilla Bug 64585 Stale ITD example code in Programming Guide --- docs/progGuideDB/semantics.xml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/progGuideDB/semantics.xml b/docs/progGuideDB/semantics.xml index da0b772b0..650cc7345 100644 --- a/docs/progGuideDB/semantics.xml +++ b/docs/progGuideDB/semantics.xml @@ -2031,25 +2031,25 @@ aspect A { - private Registry otherPackage.*.r; - public void otherPackage.*.register(Registry r) { - r.register(this); - this.r = r; + private Registry otherPackage.onType.r; + public void otherPackage.onType.register(Registry r) { + r.register(this); + this.r = r; } } - declares that every type in otherPackage has a field + declares that onType in otherPackage has a field r. This field, however, is only accessible from the code inside of aspect A. The aspect also declares - that every type in otherPackage has a method + that onType has a method "register", but makes this method accessible from everywhere. - If any type in otherPackage already defines a + If onType already defines a private or package-protected field "r", there is no conflict: The aspect cannot see such a field, and no code in otherPackage can see the inter-type @@ -2057,7 +2057,7 @@ - If any type in otherPackage defines a public field + If onType defines a public field "r", there is a conflict: The expression @@ -2072,7 +2072,7 @@ - If any type in otherPackage defines any method + If onType defines a method "register(Registry)" there is a conflict, since it would be ambiguous to any code that could see such a defined method which "register(Registry)" method was applicable. -- 2.39.5