7 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
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	e7a97e884a	value token: "=" can be part of the value.	2024-12-11 16:53:04 +01:00
Henrik Hautakoski	0512ebe640	test/corpus/values.txt: split tests	2024-12-11 12:01:38 +01:00
Henrik Hautakoski	c0d7c31981	adding license and readme	2024-12-11 11:53:53 +01:00
Henrik Hautakoski	527ac2368f	adding more number types	2024-12-11 00:43:34 +01:00
Henrik Hautakoski	adc9052da5	add integer and boolean values	2024-12-10 22:24:26 +01:00
Henrik Hautakoski	948e93ffac	Initial Commit	2024-12-10 19:51:21 +01:00