LexNameToken Comparison
In order to compare 2 lex name tokens -- either for compare(...) or equals(...) purposes -- we need type information.
This leads us to rely on external classes (usually assistants) that need to be accessed statically or we have to thread too much stuff into the tokens.
As we move away from static usage, we really need to come up with a new way to compare lex name tokens. One that doesn't rely on external classes or helpers.
As a side note, for a post-September trigger, this relates to the idea of refactoring part of the typechecker into type system module. To be discussed by me, @lausdahl, @ldcouto, and possibly @nickbattle in October.
VDMJ version 4 distinuguishes between LexNameToken (which is a pure gramatical object without type information) and TCNameToken (which is used in the type checker, and does include type information). That may not solve the issue here, but it seems relevant.