5b94b03b04
Fix user guide double backslashes in examples
2025-07-22 21:17:18 -04:00
9d686989ec
Fix C issue not fully initializing pvalues
...
This issue manifested when multiple ptypes are present with different sizes.
2025-07-22 21:05:32 -04:00
87d892d0a3
Fix a couple clang warnings
2025-07-21 23:26:37 -04:00
4ec57fa48d
Fix vim syntax highlighting for a regex ending with an escaped backslash
2025-07-20 17:16:59 -04:00
8b38ea4261
v2.2.1
2025-04-05 09:53:27 -04:00
92da10e483
Fix GC issue for D backend with AST enabled - close #36
2025-04-05 09:51:01 -04:00
839174a635
Generate comments to annotate reduce table entries
2025-04-05 09:50:18 -04:00
659de44c31
Update gems
2025-03-29 18:31:46 -04:00
207201d589
v2.2.0
2025-03-13 19:25:30 -04:00
89bc52fd80
Update CHANGELOG for v2.2.0
2025-03-13 19:25:09 -04:00
eb9d9026fc
Allow multiple lexer modes to be specified for a lexer pattern - close #35
2025-03-11 20:40:10 -04:00
54bb3307cd
Document p_decode_code_point() API function - close #34
2025-03-10 12:19:42 -04:00
5ebcbb2d6d
v2.1.1
2024-12-28 23:15:45 -05:00
61ebbb4f19
Update CHANGELOG for v2.1.1
2024-12-28 23:13:46 -05:00
1b4ca59158
Field aliases for AST node fields could alias incorrect field when multiple rule alternatives present for one rule set - close #33
2024-12-28 23:08:53 -05:00
b02c9205c0
Update CHANGELOG
2024-12-28 10:01:33 -05:00
7344554b5f
Version 2.1.0
2024-12-28 09:56:29 -05:00
77571a3449
Update gems
2024-12-28 09:54:54 -05:00
e098b7e445
Report rule name and line number for conflicting AST node field positions errors - close #32
2024-12-28 09:51:12 -05:00
3ea344a520
v2.0.0
2024-09-25 16:09:27 -04:00
530878a796
Update CHANGELOG for v2.0.0
2024-09-25 16:09:20 -04:00
1d468b6d3c
Use 1-based row and column values for position values - close #30
2024-09-25 15:58:03 -04:00
98e10d3d14
Fix named optional rules - close #29
2024-09-24 20:28:19 -04:00
36c74e439e
Log conflicting rules on reduce/reduce conflict - close #31
2024-09-24 20:05:39 -04:00
c24f323ff0
v1.5.1
2024-07-26 22:30:48 -04:00
fec2c28693
Only calculate lookahead tokens when needed - #28
...
Lookahead tokens are only need if either:
(1) There is more than one rule that could be reduced in a given parser
state, or
(2) There are shift actions for a state and at least one rule that could
be reduced in the same state (to warn about shift/reduce conflicts).
2024-07-26 22:08:25 -04:00
61339aeae9
Avoid recalculating reduce_rules - #28
2024-07-26 21:36:41 -04:00
95b3dc6550
Cache ItemSet#next_symbols - #28
2024-07-25 20:33:15 -04:00
74d94fef72
Do not build ItemSet follow sets - #28
2024-07-25 20:02:00 -04:00
588c5e21c7
Cache ItemSet#leading_item_sets return values - #28
2024-07-25 10:42:43 -04:00
5f1c306273
Update CLI usage in README
2024-07-22 21:35:32 -04:00
343e8a7f9e
v1.5.0
2024-07-22 21:23:38 -04:00
b3a134bf8d
Update vim syntax to highlight "?" and field alias names
2024-07-22 20:39:59 -04:00
4a71dc74fb
Update CHANGELOG for v1.5.0
2024-07-22 20:26:04 -04:00
a7348be95d
Add rule field aliases - #24
2024-07-22 20:16:52 -04:00
9746b3f2bf
Document position tracking fields in user guide - #27
2024-07-21 14:04:51 -04:00
c5b8fc28bd
Move INVALID_POSITION from header to C source - #27
2024-07-21 13:39:34 -04:00
092fce61eb
Test position validity for empty matching rules - #27
2024-07-21 13:39:30 -04:00
e647248e34
Track start and end position of rules in AST nodes - #27
2024-07-19 15:37:37 -04:00
f4ae1b8601
Add position fields to AST nodes (not populated yet) - #27
2024-07-19 14:34:50 -04:00
eae2e17f41
Test tracking token end positions when the token spans a newline - #27
2024-07-18 12:09:26 -04:00
87d6d29d60
Store token end position - #27
2024-07-18 12:03:44 -04:00
3aced70356
Show line numbers of rules upon conflict - close #23
2024-07-14 20:52:52 -04:00
2dd89445fc
Add command line switch to output warnings to stderr - close #26
2024-07-14 15:36:07 -04:00
4ae5ab79b3
Warn on shift/reduce conflicts
2024-07-13 21:35:53 -04:00
69cc8fa67d
Always compute lookahead tokens for reduce rules
...
Even if they won't be needed for the generated parser, they'll be useful
to detect shift/reduce conflicts.
2024-07-13 21:01:44 -04:00
7f3eb8f315
Calculate follow token set for an ItemSet
2024-07-13 20:48:28 -04:00
d76e12fea1
Rename "following" to "next" - #25
...
The term "following" could potentially imply an association with the
"follow set", however it was used in a non-closed manner.
2024-07-08 10:14:09 -04:00
911e9505b7
Track token position in AST Token node
2024-05-27 22:10:05 -04:00
aaeb0c4db1
Remove leftover TODO from earlier restructuring
2024-05-27 20:44:42 -04:00
