Some parser inputs are implicitly rejected due to EOF

[apasel422]

For example:

parser.parse('x;a')

and

parser.parse('x;a=')

throw TypeError: Cannot read properties of undefined (reading 'match'), presumably because the Parser.lookChar() method is called via Parser.parseKey and Parser.parseBareItem, respectively, without checking Parser.eof() first.

It would be nice to have better error messages in these cases, e.g. ParseError: Unexpected end of input.

Perhaps lookChar itself could call eof()?

[evert]

I agree, ideally we never throw a TypeError, and always a ParseError. I'm going to modify the unittests to check for this, I suspect that there's more cases.

[evert]

Released as v1.0.1