| java.lang.Object
 EDU.purdue.cs.bloat.context.BloatContext
EDU.purdue.cs.bloat.context.PersistentBloatContext
All known Subclasses: EDU.purdue.cs.bloat.context.CachingBloatContext,
| PersistentBloatContext | | public class PersistentBloatContext extends BloatContext (Code) | | Maintains all BLOAT data structures as if they were meant to reside in a
persistent store. As a result, it keeps every piece of BLOAT data around
because it might be needed in the future. No fancing cache maintainence is
performed. Because we are going for maximum information we take the closure
of classes when working with the class hierarchy.
|
| DB_COMMIT | | public static boolean DB_COMMIT(Code) | | |
| methodEditors | | protected Map methodEditors(Code) | | |
| PersistentBloatContext | | public PersistentBloatContext(ClassInfoLoader loader)(Code) | | Constructor. Each BloatContext stems from a
ClassInfoLoader. Using the loader it can create an
Editor and such. Initially, no classes are loaded.
|
| PersistentBloatContext | | protected PersistentBloatContext(ClassInfoLoader loader, boolean closure)(Code) | | Constructor. It is the responsibility of the subclasses to add classes to
the hierarchy by calling addClasses.
Parameters:
loader - Used to load classes
Parameters:
closure - Do we look for the maximum number of classes? |
| addClasses | | protected void addClasses(Collection classes)(Code) | | Adds a bunch of (names of) classes to the hierarchy.
|
| commit | | public void commit()(Code) | | |
| commitDirty | | public void commitDirty()(Code) | | |
| newClassInfo | | public ClassInfo newClassInfo(int modifiers, int classIndex, int superClassIndex, int[] interfaceIndexes, List constants)(Code) | | |
|
|