Ben Liblit 72c754e874 Declare private methods static wherever possible ... If a method is private, there's no risk that a subclass elsewhere might be overriding it and depending on dynamic dispatch to choose the right implementation. So all of these private methods can safely be declared static without risk of regression in either WALA code or unseen third-party code.		2017-06-07 08:29:23 -07:00
..
flowgraph	Declare private methods static wherever possible	2017-06-07 08:29:23 -07:00
FieldBasedCallGraphBuilder.java	Declare private methods static wherever possible	2017-06-07 08:29:23 -07:00
JSMethodInstructionVisitor.java	handle more cases with constructors	2014-05-28 13:35:40 -04:00
OptimisticCallgraphBuilder.java	Declare private methods static wherever possible	2017-06-07 08:29:23 -07:00
PessimisticCallGraphBuilder.java	Fix 42 Eclipse warnings about unused imports	2017-03-20 00:43:48 -05:00
WorklistBasedOptimisticCallgraphBuilder.java	cross-cutting changes to make more of WALA runnable with TeaVM. The biggest change is refactoring to AnalysisCache and friends; since TeaVM does not support SoftReference, I needed to add a layer of interfaces so that I can use a more simpleminded caching implementation for TeaVM. There are other changes to Module and friends to break connections with File and URL, which also cause TeaVM grief. I also organized imports in many places to remove unused types that caused trouble.	2017-02-02 20:33:27 -05:00