1f5baa64dd
build: regenerate parser
2026-07-14 20:50:13 +02:00
b109061d77
add support for export keyword
2026-07-14 20:41:22 +02:00
dependabot[bot]
8254f01fdb
build: regenerate parser [dependabot skip]
2026-07-12 11:52:52 +00:00
03e53646dd
chore: version v1.0.0
2026-07-06 14:50:33 +02:00
dependabot[bot]
0ed3135003
build: regenerate parser [dependabot skip]
2026-07-05 11:52:58 +00:00
0bba6d6859
v0.0.7
2026-04-14 10:29:43 +02:00
dependabot[bot]
1be5c56459
build: regenerate parser [dependabot skip]
2026-03-01 11:59:41 +00:00
7878ce1646
v0.0.5
2026-02-08 09:45:45 +01:00
8bae258c71
src/scanner.c: advanceWS should be static
2026-02-08 09:43:52 +01:00
67b30407dd
update genereted parser files
2026-02-08 09:43:52 +01:00
7223d87d9e
adding variable support
2024-12-12 19:22:14 +01:00
8c66bd3605
make string_content optional instead of matching empty values.
2024-12-12 17:23:37 +01:00
4d71a8548b
make no distinction between single quoted and double quoted string tokens.
2024-12-12 17:05:31 +01:00
dabedec847
adding hexadecimal and decimal as a subtoken for integer
2024-12-12 16:55:10 +01:00
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
527ac2368f
adding more number types
2024-12-11 00:43:34 +01:00
adc9052da5
add integer and boolean values
2024-12-10 22:24:26 +01:00
948e93ffac
Initial Commit
2024-12-10 19:51:21 +01:00
