Fix top-level use statements

[benesch]

Given a namespaced file which uses a top-level name like

namespace mindplay;

use PDO;

the parser will incorrectly generate the following uses information:

array('DO' => 'PDO')

This commit adjusts the parser to handle use statements which import a
name without a namespace separator.

[benesch]

It's worth noting that the "HandlesMethodAliasingWithTraits" test case in #102 should be failing without this fix—but it's not due to #104!

[aik099]

Where DO word would come from during use statement parsing, that you've mentioned in issue description?

[aik099]

Maybe it's better to be written as if/else without ternary operator to be more readable. Now the 1 + -1 construct that is evaluated at the end is a bit confusing.

[aik099]

Today’s review completed.

[benesch]

DO is the result of an off-by-one error on PDO. I've updated the code to use explode and array_pop, which is the most readable method I could come up with.

[aik099]

This line uses the explode function side effect that if char for explode wasn't found in a string the whole string is returned as 1st array element.

It's better to be more specific (this code will replace this and following line):

if (strpos($use, '\\') !== false) {
    $uses[substr($use, 1 + strrpos($use, '\\'))] = $use;
}
else {
    $uses[$use] = $use;
}

[aik099]

Today’s review completed.

[benesch]

Adjusted as requested!

[aik099]

Looks good. Merging. Thanks, @benesch .