Class JSAnalysisOptions

java.lang.Object

com.ibm.wala.ipa.callgraph.AnalysisOptions

com.ibm.wala.cast.js.ipa.callgraph.JSAnalysisOptions

public class JSAnalysisOptions
extends AnalysisOptions

call graph construction options specific to JavaScript.

Nested Class Summary

Nested classes/interfaces inherited from class AnalysisOptions

AnalysisOptions.ReflectionOptions

Modifier and Type	Class	Description
static enum	AnalysisOptions.ReflectionOptions	options for handling reflection during call graph construction

Constructor Summary

Constructors

Constructor	Description
JSAnalysisOptions(AnalysisScope scope, Iterable<? extends Entrypoint> e)

Method Summary

Modifier and Type	Method	Description
boolean	handleCallApply()	should the analysis model the semantics of Function.prototype.call / apply?
void	setHandleCallApply(boolean handleCallApply)
void	setUseLoadFileTargetSelector(boolean useIt)
boolean	useLoadFileTargetSelector()

Methods inherited from class AnalysisOptions

getAnalysisScope, getClassTargetSelector, getEntrypoints, getHandleStaticInit, getHandleZeroLengthArray, getMaxEvalBetweenTopo, getMaxNumberOfNodes, getMethodTargetSelector, getMinEquationsForTopSort, getReflectionOptions, getSSAOptions, getTopologicalGrowthFactor, getTraceStringConstants, getUseConstantSpecificKeys, getUseLexicalScopingForGlobals, getUseStacksForLexicalScoping, setAnalysisScope, setEntrypoints, setHandleStaticInit, setHandleZeroLengthArray, setMaxEvalBetweenTopo, setMaxNumberOfNodes, setMinEquationsForTopSort, setReflectionOptions, setSelector, setSelector, setSSAOptions, setTopologicalGrowthFactor, setTraceStringConstants, setUseConstantSpecificKeys, setUseLexicalScopingForGlobals, setUseStacksForLexicalScoping

Modifier and Type	Method	Description
AnalysisScope	getAnalysisScope()
ClassTargetSelector	getClassTargetSelector()
Iterable<? extends Entrypoint>	getEntrypoints()	TODO: this really should go away.
boolean	getHandleStaticInit()	Should call graph construction handle possible invocations of static initializer methods?
boolean	getHandleZeroLengthArray()	Should call graph construction handle arrays of zero-length differently?
int	getMaxEvalBetweenTopo()
long	getMaxNumberOfNodes()
MethodTargetSelector	getMethodTargetSelector()
int	getMinEquationsForTopSort()
AnalysisOptions.ReflectionOptions	getReflectionOptions()	Should call graph construction attempt to handle reflection via detection of flows to casts, analysis of string constant parameters to reflective methods, etc.?
SSAOptions	getSSAOptions()
double	getTopologicalGrowthFactor()
boolean	getTraceStringConstants()	Should analysis try to understand the results of string constants flowing to a + operator? Note that this option does not apply to Java bytecode analysis, since the + operators have been compiled away for that.
boolean	getUseConstantSpecificKeys()	Use distinct instance keys for distinct string constants?
boolean	getUseLexicalScopingForGlobals()	Should global variables be considered lexically-scoped from the root node?
boolean	getUseStacksForLexicalScoping()	Should analysis of lexical scoping consider call stacks?
void	setAnalysisScope(AnalysisScope analysisScope)
void	setEntrypoints(Iterable<? extends Entrypoint> entrypoints)
void	setHandleStaticInit(boolean handleStaticInit)	Should call graph construction handle possible invocations of static initializer methods?
void	setHandleZeroLengthArray(boolean handleZeroLengthArray)	Should call graph construction handle arrays of zero-length differently?
void	setMaxEvalBetweenTopo(int i)
void	setMaxNumberOfNodes(long maxNumberOfNodes)
void	setMinEquationsForTopSort(int i)
void	setReflectionOptions(AnalysisOptions.ReflectionOptions reflectionOptions)	Should call graph construction attempt to handle reflection via detection of flows to casts, analysis of string constant parameters to reflective methods, etc.?
void	setSelector(ClassTargetSelector x)	install a class target selector
void	setSelector(MethodTargetSelector x)	install a method target selector
void	setSSAOptions(SSAOptions ssaOptions)
void	setTopologicalGrowthFactor(double d)
void	setTraceStringConstants(boolean v)	Should analysis try to understand the results of string constants flowing to a + operator? Note that this option does not apply to Java bytecode analysis, since the + operators have been compiled away for that.
void	setUseConstantSpecificKeys(boolean useConstantSpecificKeys)	Use distinct instance keys for distinct string constants?
void	setUseLexicalScopingForGlobals(boolean v)	Should global variables be considered lexically-scoped from the root node?
void	setUseStacksForLexicalScoping(boolean v)	Should analysis of lexical scoping consider call stacks?

Methods inherited from class Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

JSAnalysisOptions

public JSAnalysisOptions(AnalysisScope scope,
 Iterable<? extends Entrypoint> e)

Method Details

handleCallApply

public boolean handleCallApply()

should the analysis model the semantics of Function.prototype.call / apply?

setHandleCallApply

public void setHandleCallApply(boolean handleCallApply)

useLoadFileTargetSelector

public boolean useLoadFileTargetSelector()

setUseLoadFileTargetSelector

public void setUseLoadFileTargetSelector(boolean useIt)