Julian Dolby 38c5de6160 fix for forName selector: use the CHA in getRelevantParameters to resolve ... the declared target of the call site. This is needed to make sure forName targets loaded with the Application loader get resolved to point to the real metod reference for forName. this issue actually manifested itself in the Kawa Chess program, and so I have added an assertion to make sure this resolution is done properly.		2018-10-18 22:25:21 -04:00
..
analysis	fix for forName selector: use the CHA in getRelevantParameters to resolve	2018-10-18 22:25:21 -04:00
cfg	rename getNumberOfParameters to getNumberOfPositionalParameters since the Python front end now supports keyword parameters	2018-04-12 19:09:25 -04:00
classLoader	support for method argument default values	2018-10-17 19:44:44 -04:00
client	Resolve the last two Eclipse warnings about using raw types	2018-04-13 12:53:33 -05:00
core/plugin	more conversion to Unix line endings	2012-09-04 15:59:50 -07:00
dataflow	"@param" parameter name must match the name of some formal parameter	2017-12-19 16:53:55 -06:00
demandpa	Impl of IMethod.is(Wala)Synthetic and IClass.isSynthetic (#359)	2018-10-02 22:28:21 -07:00
escape	"@returns" is not a valid Javadoc tag, but "@return" is	2017-12-19 16:53:55 -06:00
ipa	1) a bit more source mappimg information	2018-10-13 08:42:08 -04:00
model	Remove a Java bytecode file that shouldn't be revision-tracked	2018-05-21 16:15:53 -05:00
properties	Plug an `InputStream` resource leak	2017-08-27 11:03:14 -07:00
ssa	Impl of IMethod.is(Wala)Synthetic and IClass.isSynthetic (#359)	2018-10-02 22:28:21 -07:00
types	more support for method handles, particularly for ones created with	2018-08-02 19:35:32 -04:00
util	a little tolerance for sloppy models	2018-07-04 15:46:06 -04:00
viz	Remove useless "@return" tags with no descriptive text	2017-12-19 16:53:56 -06:00