From d079132c07c4b43551994d1b853a141e3a79db3a Mon Sep 17 00:00:00 2001 From: dolby-oss Date: Fri, 12 Jun 2009 13:00:29 +0000 Subject: [PATCH] fix type-o in comment git-svn-id: https://wala.svn.sourceforge.net/svnroot/wala/trunk@3646 f5eafffb-2e1d-0410-98e4-8ec43c5233c4 --- .../com/ibm/wala/cast/java/ssa/EnclosingObjectReference.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/com.ibm.wala.cast.java/src/com/ibm/wala/cast/java/ssa/EnclosingObjectReference.java b/com.ibm.wala.cast.java/src/com/ibm/wala/cast/java/ssa/EnclosingObjectReference.java index 106096a26..6dae54b6f 100644 --- a/com.ibm.wala.cast.java/src/com/ibm/wala/cast/java/ssa/EnclosingObjectReference.java +++ b/com.ibm.wala.cast.java/src/com/ibm/wala/cast/java/ssa/EnclosingObjectReference.java @@ -9,7 +9,7 @@ import com.ibm.wala.ssa.SymbolTable; import com.ibm.wala.types.TypeReference; /** - * The CAst source language front end for Java has explicit support for lexicallly-enclosing objects, rather than compiling them + * The CAst source language front end for Java has explicit support for lexically-enclosing objects, rather than compiling them * away into extra fields and access-control thwarting accessor methods as is done in bytecode. This instruction represents a read * of the object of the given type that lexically encloses its use value. *