Position info fix: avoid using previous token

This fixes a position info problem where a tree node node could be assigned a starting and ending token where the ending token occurs before the starting one.

It's a small patch, that simply checks if the starting token is the same as the current token. If it is the same, the parser shouldn't use the previous token as the ending token.

@ajaxorg/liskov