Update grammar to correctly produce value token

Browse source

Problem was before that for example the input [0x000KKK] would produce a
hexadecimal and a value token (for the respective parts)

However, the more correct way is to have the whole input identified as a
value token. basicly if the whole input between "=" and a special
"end-of-assignment" token can't be identified as a string,bool,integer
whatever. it should be identified as a value token.

...

This commit is contained in:

Henrik Hautakoski 2024-12-12 10:55:11 +01:00

parent e7a97e884a

commit d0b54d61aa

8 changed files with 427 additions and 539 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

735

src/parser.c generated

View file

File diff suppressed because it is too large Load diff