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
..
.settings	Suppress Eclipse warnings about potentially-static methods	2017-06-07 08:29:23 -07:00
META-INF	update version to 1.4.3-SNAPSHOT	2017-04-19 09:19:09 -07:00
src/com/ibm/wala	Declare private methods static wherever possible	2017-06-07 08:29:23 -07:00
.classpath	Use consistent Java versions, usually 1.7	2016-11-29 21:29:30 -06:00
.gitignore	[releng] added preliminary maven tycho build support	2013-04-29 13:13:22 +02:00
.project	move some functionality to wala.util	2011-01-17 20:56:35 +00:00
build.properties	Fix warnings about unset javacProjectSettings build entries (#176)	2017-05-04 11:44:32 -07:00
mvncentral.xml	update version to 1.4.3-SNAPSHOT	2017-04-19 09:19:09 -07:00
pom.xml	update version to 1.4.3-SNAPSHOT	2017-04-19 09:19:09 -07:00