From bd70bd2a8ce2c95d0768ad7786031b8cb068b2f5 Mon Sep 17 00:00:00 2001 From: aclement Date: Tue, 3 Jan 2012 17:44:44 +0000 Subject: [PATCH] spelling --- weaver/src/org/aspectj/weaver/bcel/BcelAdvice.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/weaver/src/org/aspectj/weaver/bcel/BcelAdvice.java b/weaver/src/org/aspectj/weaver/bcel/BcelAdvice.java index 4d2e9bb85..ac30af5f9 100644 --- a/weaver/src/org/aspectj/weaver/bcel/BcelAdvice.java +++ b/weaver/src/org/aspectj/weaver/bcel/BcelAdvice.java @@ -323,14 +323,14 @@ class BcelAdvice extends Advice { } else if (getKind() == AdviceKind.After) { shadow.weaveAfter(this); } else if (getKind() == AdviceKind.Around) { - // Note: under regular LTW the aspect is usually loaded after the first use of any class affecteted by it + // Note: under regular LTW the aspect is usually loaded after the first use of any class affected by it. // This means that as long as the aspect has not been thru the LTW, it's woven state is unknown // and thus canInline(s) will return false. // To force inlining (test), ones can do Class aspect = FQNAspect.class in the clinit of the target class // FIXME AV : for AJC compiled @AJ aspect (or any code style aspect), the woven state can never be known // if the aspect belongs to a parent classloader. In that case the aspect will never be inlined. // It might be dangerous to change that especially for @AJ aspect non compiled with AJC since if those - // are not weaved (f.e. use of some limiteed LTW etc) then they cannot be prepared for inlining. + // are not weaved (f.e. use of some limited LTW etc) then they cannot be prepared for inlining. // One solution would be to flag @AJ aspect with an annotation as "prepared" and query that one. LazyClassGen enclosingClass = shadow.getEnclosingClass(); if (enclosingClass != null && enclosingClass.isInterface() && shadow.getEnclosingMethod().getName().charAt(0) == '<') { -- 2.39.5