DISPLAY_IDENTIFIER that starts with a number causes a tokenization exception about a2lfile HOT 4 CLOSED

Identifiers in a2l files are not allowed to start with digits. In fact only numeric literals can contain a digit in the first position.

Accordingly, the tokenizer sees a numeric literal when it encounters the '1' of "1ms", then it considers 'm' to be the beginning of the next token and complains about missing whitespace between the two.

from a2lfile.

I should add that various tools have different levels of "standard compliance". It's possible that your file was created and processed without complaint by some other application. In that case it may be worth adding some kind of compatibility workaround.

from a2lfile.

Thank you @DanielT for the quick response. I would also like to add that this tool is amazing. It is much more robust than the other a2l parsers available on Github. Great work !

from a2lfile.

You're welcome.
I thought about this some more and decided that a code change is needed after all: There should be better error messages in this case. I'm changing this case to produce a ParserError::InvalidIdentifier instead of the confusing MissingWhitespace error.

from a2lfile.