lrama 0.6.10 → 0.6.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3fce10e3be7a24cd5dcae139d72e41bb586cb2a34bb6a6cd06412a420e65513b
-  data.tar.gz: 663d42179f28318ecb2a120d726dfcdfc8f599f2732771d39ed2d6a9e88fe07d
+  metadata.gz: 1d566a5097f0fd579e70f94769cca4e68a8f0e810e10cd55556583b1c2653945
+  data.tar.gz: e5ab505df1a8fffe46a9f526456b593db786f36f0e998e7e3acbf5f68b76d9a9
 SHA512:
-  metadata.gz: 469a0e7bf84b68092e90187df12d7c9a71273e26caded2b27742cb7a83930a76626f73f2f872c931f496816348005a986d7edce639c326f7a83ed697708b4013
-  data.tar.gz: f053199c82ca39d614c56c55fd09daeb441e7e3b7504165042ee3c6a1275c400d640822365d939145a3a7a6c791da63119e614c4e5a36ad4f0cfa57a7561baa4
+  metadata.gz: 753a7b6f0781f6b0bd2db8c98ef0e6171496d6fd8a2a16762b67dc471e34b4118b4439b89facc1915a364d4c4823edaef464d947cbda3d913ebd8eff87d91b76
+  data.tar.gz: 7f953657c7050c7d527bf190d284e5b56b3df5b92c2034d5f4425f73be1e21208d1869a4ffe6c9091b4adf79671e71865000797ec2d7ed1ad66cfe5d1846cd7b

data/.github/workflows/test.yaml

@@ -186,4 +186,8 @@ jobs:
       - run: ../autogen.sh
       - run: ../configure -C --disable-install-doc
       - run: make
-      - run: make test-all
+      - run: make test-all RUN_OPTS="$RUN_OPTS" SPECOPTS="$SPECOPTS"
+        env:
+          EXCLUDES: '../test/.excludes-parsey'
+          RUN_OPTS: ${{ matrix.run_opts || '--parser=parse.y' }}
+          SPECOPTS: ${{ matrix.specopts || '-T --parser=parse.y' }}

data/Gemfile

@@ -15,6 +15,6 @@ gem "memory_profiler"
 # Recent steep requires Ruby >= 3.0.0.
 # Then skip install on some CI jobs.
 if !ENV['GITHUB_ACTION'] || ENV['INSTALL_STEEP'] == 'true'
-  gem "rbs", "3.5.3", require: false
-  gem "steep", "1.7.1", require: false
+  gem "rbs", "3.7.0", require: false
+  gem "steep", "1.9.1", require: false
 end

data/NEWS.md

@@ -1,12 +1,47 @@
 # NEWS for Lrama
 
+## Lrama 0.6.11 (2024-12-23)
+
+### Add support for %type declarations using %nterm in Nonterminal Symbols
+
+Allow to use `%nterm` in Nonterminal Symbols for `%type` declarations.
+
+```yacc
+%nterm <type> nonterminal…
+```
+
+This directive is also supported for compatibility with Bison, and only non-terminal symbols are allowed. In other words, definitions like the following will result in an error:
+
+```yacc
+%{
+// Prologue
+%}
+
+%token EOI 0 "EOI"
+%nterm EOI
+
+%%
+
+program: /* empty */
+        ;
+```
+
+It show an error message like the following:
+
+```command
+❯ exe/lrama nterm.y
+nterm.y:6:7: symbol EOI redeclared as a nonterminal
+%nterm EOI
+       ^^^
+```
+
 ## Lrama 0.6.10 (2024-09-11)
 
 ### Aliased Named References for actions of RHS in parameterizing rules
 
 Allow to use aliased named references for actions of RHS in parameterizing rules.
 
-```
+```yacc
 %rule sum(X, Y): X[summand] '+' Y[addend] { $$ = $summand + $addend }
                ;
 ```
@@ -18,7 +53,7 @@ https://github.com/ruby/lrama/pull/410
 
 Allow to use named references for actions of RHS in parameterizing rules caller side.
 
-```
+```yacc
 opt_nl: '\n'?[nl] <str> { $$ = $nl; }
       ;
 ```
@@ -29,7 +64,7 @@ https://github.com/ruby/lrama/pull/414
 
 Allow to define parameterizing rules in the middle of the grammar.
 
-```
+```yacc
 %rule defined_option(X): /* empty */
                        | X
                        ;
@@ -52,8 +87,8 @@ https://github.com/ruby/lrama/pull/420
 Support to report unused terminal symbols.
 Run `exe/lrama --report=terms` to show unused terminal symbols.
 
-```
-❯ exe/lrama --report=terms sample/calc.y
+```console
+$ exe/lrama --report=terms sample/calc.y
  11 Unused Terms
      0 YYerror
      1 YYUNDEF
@@ -74,8 +109,8 @@ https://github.com/ruby/lrama/pull/439
 Support to report unused rules.
 Run `exe/lrama --report=rules` to show unused rules.
 
-```
-❯ exe/lrama --report=rules sample/calc.y
+```console
+$ exe/lrama --report=rules sample/calc.y
   3 Unused Rules
      0 unused_option
      1 unused_list
@@ -96,8 +131,8 @@ https://github.com/ruby/lrama/pull/446
 Support to warning redefined parameterizing rules.
 Run `exe/lrama -W` or  `exe/lrama --warnings` to show redefined parameterizing rules.
 
-```
-❯ exe/lrama -W sample/calc.y
+```console
+$ exe/lrama -W sample/calc.y
 parameterizing rule redefined: redefined_method(X)
 parameterizing rule redefined: redefined_method(X)
 ```
@@ -117,7 +152,7 @@ https://github.com/ruby/lrama/pull/457
 
 Allow to specify tag on callee side of parameterizing rules.
 
-```
+```yacc
 %union {
     int i;
 }
@@ -130,7 +165,7 @@ Allow to specify tag on callee side of parameterizing rules.
 
 Allow to use named references for actions of RHS in parameterizing rules.
 
-```
+```yacc
 %rule option(number): /* empty */
                     | number { $$ = $number; }
                     ;
@@ -142,7 +177,7 @@ Allow to use named references for actions of RHS in parameterizing rules.
 
 Allow to nested parameterizing rules with tag.
 
-```
+```yacc
 %union {
     int i;
 }
@@ -179,8 +214,8 @@ User can use `'symbol'?`, `'symbol'+` and `'symbol'*` in RHS of user defined par
 Support trace actions for debugging.
 Run `exe/lrama --trace=actions` to show grammar rules with actions.
 
-```
-❯ exe/lrama --trace=actions sample/calc.y
+```console
+$ exe/lrama --trace=actions sample/calc.y
 Grammar rules with actions:
 $accept -> list, YYEOF {}
 list -> ε {}
@@ -199,7 +234,7 @@ expr -> '(', expr, ')' { $$ = $2; }
 Support inlining for rules.
 The `%inline` directive causes all references to symbols to be replaced with its definition.
 
-```
+```yacc
 %rule %inline op: PLUS { + }
                 | TIMES { * }
                 ;
@@ -213,7 +248,7 @@ expr : number { $$ = $1; }
 
 as same as
 
-```
+```yacc
 expr : number { $$ = $1; }
      | expr '+' expr { $$ = $1 + $3; }
      | expr '*' expr { $$ = $1 * $3; }
@@ -226,7 +261,7 @@ expr : number { $$ = $1; }
 
 User can specify the type of mid rule action by tag (`<bar>`) instead of specifying it with in an action.
 
-```
+```yacc
 primary: k_case expr_value terms?
            {
                $<val>$ = p->case_labels;
@@ -241,7 +276,7 @@ primary: k_case expr_value terms?
 
 can be written as
 
-```
+```yacc
 primary: k_case expr_value terms?
            {
                $$ = p->case_labels;
@@ -266,7 +301,7 @@ Bison supports this feature from 3.1.
 
 Support `preceded`, `terminated` and `delimited` rules.
 
-```
+```text
 program: preceded(opening, X)
 
 // Expanded to
@@ -302,7 +337,7 @@ In general, these resources are freed by actions or after parsing.
 However if syntax error happens in parsing, these codes may not be executed.
 Codes associated to `%destructor` are executed when semantic value is popped from the stack by an error.
 
-```
+```yacc
 %token <val1> NUM
 %type <val2> expr2
 %type <val3> expr
@@ -350,7 +385,7 @@ Lrama provides these five callbacks. Registered functions are called when each e
 User also needs to access semantic value of their stack in grammar action. `$:n` provides the way to access to it. `$:n` is translated to the minus index from the top of the stack.
 For example
 
-```
+```yacc
 primary: k_if expr_value then compstmt if_tail k_end
           {
           /*% ripper: if!($:2, $:4, $:5) %*/
@@ -375,7 +410,7 @@ https://github.com/ruby/lrama/pull/344
 
 Allow to pass an instantiated rule to other parameterizing rules.
 
-```
+```yacc
 %rule constant(X) : X
                   ;
 
@@ -392,7 +427,7 @@ program         : option(constant(number)) // Nested rule
 
 Allow to use nested parameterizing rules when define parameterizing rules.
 
-```
+```yacc
 %rule option(x) : /* empty */
                 | X
                 ;
@@ -419,7 +454,7 @@ https://github.com/ruby/lrama/pull/337
 
 Allow to define parameterizing rule by `%rule` directive.
 
-```
+```yacc
 %rule pair(X, Y): X Y { $$ = $1 + $2; }
                 ;
 
@@ -442,7 +477,7 @@ https://github.com/ruby/lrama/pull/285
 Allow to specify type of rules by specifying tag, `<i>` in below example.
 Tag is post-modification style.
 
-```
+```yacc
 %union {
     int i;
 }
@@ -469,7 +504,7 @@ https://github.com/ruby/lrama/pull/197
 
 Support `separated_list` and `separated_nonempty_list` parameterizing rules.
 
-```
+```text
 program: separated_list(',', number)
 
 // Expanded to
@@ -500,7 +535,7 @@ https://github.com/ruby/lrama/pull/204
 Parameterizing rules are template of rules.
 It's very common pattern to write "list" grammar rule like:
 
-```
+```yacc
 opt_args: /* none */
         | args
         ;
@@ -532,7 +567,7 @@ https://github.com/ruby/lrama/pull/62
 
 ### Runtime configuration for error recovery
 
-Meke error recovery function configurable on runtime by two new macros.
+Make error recovery function configurable on runtime by two new macros.
 
 * `YYMAXREPAIR`: Expected to return max length of repair operations. `%parse-param` is passed to this function.
 * `YYERROR_RECOVERY_ENABLED`: Expected to return bool value to determine error recovery is enabled or not. `%parse-param` is passed to this function.
@@ -555,7 +590,7 @@ https://github.com/ruby/lrama/pull/44
 Instead of positional references like `$1` or `$$`,
 named references allow to access to symbol by name.
 
-```
+```yacc
 primary: k_class cpath superclass bodystmt k_end
            {
              $primary = new_class($cpath, $bodystmt, $superclass);
@@ -564,7 +599,7 @@ primary: k_class cpath superclass bodystmt k_end
 
 Alias name can be declared.
 
-```
+```yacc
 expr[result]: expr[ex-left] '+' expr[ex.right]
                 {
                   $result = $[ex-left] + $[ex.right];

data/Steepfile

@@ -7,11 +7,14 @@ target :lib do
   signature "sig"
 
   check "lib/lrama/grammar"
+
+  check "lib/lrama/counterexamples"
   check "lib/lrama/lexer"
   check "lib/lrama/report"
   check "lib/lrama/state"
   check "lib/lrama/states"
   check "lib/lrama/bitmap.rb"
+  check "lib/lrama/counterexamples.rb"
   check "lib/lrama/digraph.rb"
   check "lib/lrama/grammar.rb"
   check "lib/lrama/options.rb"