Markus Schmidt
Markus Schmidt
almost everything is quite verbose in a jimple file: i guess then we should print (and parse) the exceptiontype in `@caughtexceptionref`, too
- [ ] print them. - [ ] parse them with JimpleParser
see Java7EnhancementTests.testTryWithResourcesStatement()
e.g. see TryCatchFinally.tryCatchNested() tests in the sourcecodefronted: - the first try block is not covered!
because: annoying to use/read in `instanceOf`
ForwardsAnalysis etc. into core module.
enables to resolve only classes that are visible to the startPackage via View (incorporate into ' AbstractView.getClasses( PackageName startPackage, ClassType classType )' )and can support with Visibility checks in general....
- [ ] replace occurences of new Collection( **size** ) calls and replace them with guavas Map.new*Collection*WithExpectedSize( **size**) to avoid resizing the backing datastructure while inserting the expected amount of...
as our Position model resembles a range like in LSP