HTTP/1.1 -1 Read error in cache disk data: SuccessContent-Type: text/csv; charset="utf-8" Last-Modified: Sat, 22 Jan 2022 03:14:08 GMT Content-length: 1710 Connection: Close Proxy-Connection: Close X-Cache: HIT from web1.osuosl.org Server: ProxyTrack 0.5 (HTTrack 3.49.2) id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,lang,patch,platform 1447,[NQP-rx] failure to capture two duplicate subrules in the same rule,allison,pmichaud,"I ran into a problem with nqp-rx grammars in a mini-language I'm working on. Looks like it might be a bug in nqp-rx, though I'm always suspicious that cases like this might be a bug in the language grammar (if it's the latter, you can close the ticket, since the language has switched to true operator precedence parsing). With two identical subrules matching in a rule, only the second result is captured in the parse tree. So a rule like: {{{ }}} Matches as: {{{ PMC 'Regex;Match' => ""IF 2 < 1\n..."" @ 38 { => PMC 'Regex;Match' => ""<"" @ 43 => PMC 'Regex;Match' => ""IF"" @ 38 => PMC 'Regex;Match' => ""1\n "" @ 45 { [...] } }}} I was hoping to be able to duplicate the problem in an isolated case, but a simplified grammar like the following creates an array of as you would expect. {{{ token TOP { } rule foo { 'foo' | 'oof' } token bar { 'bar' } }}} So far, I've only been able to duplicate the bug with the full language grammar, so, I've put a copy of the language at that version up on http://pub.lohutok.net/nqp/camle-0.0.1b-ar9319.tar.gz. Run 'make parrot', 'make', and then './camle --target=parse twosubrule.le' to produce the output above. ",bug,closed,normal,,nqp,2.0.0,medium,invalid,,,,, ,geneva,sans-serif; ">The ope