Merge branch 'hotfix/fix'
fix
Merge pull request #29 from ThomasGP/develop

Refactored and simplified toDex part
Merge branch 'hotfix/fix-for-method-resolution' into develop
Translate some UTF-8 characters to ASCII.
Translate UTF-8 characters to ascii.
Translate UTF-8 characters to ascii.
reverting commit a91e5734831564d247d1fd733b169fc37cc9cc8e as it causes problems with typing of arrays in Java
see https://github.com/Sable/soot/issues/30
Merge pull request #31 from quentin/fix-nonascii-characters

Fix nonascii characters
fix (?) for null pointer exception raised by some android apps; see
email by Damien Octeau
bugfix: DexLibWrapper could cause a stack overflow because it was only put into the cache after the recursive call had finished
Fix for issue #32
Merge pull request #33 from malaverdiere/develop

Fix for issue #32
Identation fixes.
StronglyConnectedComponentsFast accepts multi-headed directed graph.
Merge pull request #34 from quentin/feature-multiheads-scc

Feature multiheads scc
made a few modifications to the type assigner, avoiding ClassCastExceptions;

as Damien Octeau writes:

"I found a couple more places in Soot where there were some issues:

In soot/FastHierarchy.java, in method canStoreType(), around line 245:
  - the last case is currently: else { ArrayType aChild = (ArrayType) child;
I saw a case where the cast threw an exception. I replaced the else with else if (child instanceof ArrayType). I added a new else which just returns false.

In soot/jimple/toolkits/typing/integer/ConstraintChecker.java, in method caseAssignStmt(), around line 228:
  - the case if (!(baset instanceof NullType)) is followed by a cast of baset to ArrayType. I found a case where this cast caused a problem. I changed the condition to if (baset instanceof ArrayType).

In soot/jimple/toolkits/typing/integer/ConstraintCollector.java, in method caseAssignStmt(), around line 169, there is the same problem as above: a cast to ArrayType follows a condition different from if (baset instanceof ArrayType). Changing the condition as above solves the problem."