4 commits

Author	SHA1	Message	Date
Henrik Hautakoski	b0e11dc786	fix: parse multi-word unquoted string values	2026-07-22 19:53:49 +02:00
Henrik Hautakoski	4d71a8548b	make no distinction between single quoted and double quoted string tokens.	2024-12-12 17:05:31 +01:00
Henrik Hautakoski	d0b54d61aa	Update grammar to correctly produce value token ... 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.	2024-12-12 10:55:11 +01:00
Henrik Hautakoski	948e93ffac	Initial Commit	2024-12-10 19:51:21 +01:00