softdevteam/grmtools

Issues

• Make generated parsers usable on the web

  #461 opened 5 months ago by stephanemagnenat
  2

• Define lexemes in terms of other lexemes

  #465 opened 5 months ago by bendrissou
  1

• Errors in catching incorrectly terminated productions

  #463 opened 5 months ago by bendrissou
  4

• How to use the code generated by grmtools as a lib for others to use

  #455 opened 6 months ago by liluyue
  6

• Is there a way to pass Conext in `$lexer` when doing action?

  #454 opened 6 months ago by Taylor-lagrange
  3

• lrpar:%prec not followed by token name

  #450 opened 6 months ago by liluyue
  11

• lpar:Unused rule

  #452 opened 6 months ago by liluyue
  6

• lrlex: match beginning of line

  #449 opened 6 months ago by liluyue
  4

• nimbleparse:Suggestions for outputting information

  #448 opened 6 months ago by liluyue
  5

• lrpar lose info about debug

  #446 opened 6 months ago by liluyue
  7

• Docs Question - Optional Prefix to Regular Expressions

  #438 opened 9 months ago by DavidHVernon
  5

• Detailed debug info for reduce/reduce shift/reduce errors?

  #425 opened 10 months ago by DavidHVernon
  27

• From repair sequence to repaired input strings

  #279 opened 3 years ago by josepablocam
  4

• Online Yacc/Lex editor/tester

  #422 opened a year ago by mingodad
  6

• Trying to replicate `tinylang.yy` and `tinylang.l` syntax with `nimbleparse`

  #418 opened a year ago by jymchng
  5

• Weird that `nimbleparse` works on `java7.y` `java7.l` even though the `GT` symbol in both is different.

  #420 opened a year ago by jymchng
  1

• Support lex-style definitions

  #417 opened a year ago by FranklinChen
  1

• Permit stack operations on start conditions

  #325 opened 2 years ago by SMartinScottLogic
  28

• Add support for comments in lrlex files

  #403 opened 2 years ago by FranklinChen
  3

• Nondeterministic generation of Rust code

  #405 opened a year ago by FranklinChen
  2

• Explain why Copy is required for a type specified %parse-param

  #404 opened a year ago by FranklinChen
  7

• Error span improvements

  #300 opened 2 years ago by ratmice
  1

• error when using fake UMINUS token in %prec directive

  #399 opened 2 years ago by yuanweixin
  9

• GDB Support?

  #401 opened 2 years ago by madhavpcm
  5

• Request for example of handling string literals in lexer

  #398 opened 2 years ago by yuanweixin
  2

• Is there a way to avoid global variables for compile time data structures?

  #397 opened 2 years ago by 0xadeeb
  5

• Bug in grmtools documentation - traits not displaying required method names

  #396 opened 2 years ago by Benjscho
  12

• Order of execution of grammar statements?

  #392 opened 2 years ago by madhavpcm
  7

• Would be nice to have an online playground

  #385 opened 2 years ago by mingodad
  8

• Adding a %grammar-kind declaration?

  #349 opened 2 years ago by ratmice
  2

• Is it possible to perform side effects while parsing?

  #377 opened 2 years ago by loewenheim
  3

• %ignore like in flex

  #376 opened 2 years ago by madhavpcm
  8

• Broken links for YACC and LEX Manual in grmtools-book

  #374 opened 2 years ago by madhavpcm
  5

• Generated code incompatible with `-D rust-2018-idioms`

  #364 opened 2 years ago by shayne-fletcher
  7

• write .l with var for lrlex

  #361 opened 2 years ago by RickSKy
  1

• how to use lrlex with rust code

  #360 opened 2 years ago by RickSKy
  1

• how to use “ and space with .l file

  #359 opened 2 years ago by RickSKy
  4

• Remove debug formatting in non-debug locations

  #323 opened 2 years ago by ltratt
  2

• Apparently infinite recursive rule

  #290 opened 3 years ago by ratmice
  5

• The way we serialise output makes cross compiling across architectures hard

  #328 opened 2 years ago by ltratt
  1

• Break `>>` into `>` and `>`

  #301 opened 2 years ago by romdotdog
  3

• token_span sometimes returns the wrong span

  #296 opened 2 years ago by ratmice
  2

• adding a nimbleparse.toml

  #282 opened 3 years ago by ratmice
  7

• Repair not following grammar

  #280 opened 3 years ago by duskybomb
  5

• Panicked with 'called `Result::unwrap()` on an `Err` value: Custom("invalid value: integer `4984270261285729579`, expected usize")' after compiling to WebAssembly and running on nodejs

  #277 opened 3 years ago by JohnGouwar
  2

• Does it support two parser in one project?

  #270 opened 3 years ago by MrZLeo
  12

• Add support for %expect

  #234 opened 4 years ago by ltratt
  0

• Question: A good idea to call line_col at every node?

  #228 opened 4 years ago by arjunguha
  3

• out of date example in README.md

  #226 opened 4 years ago by rohany
  1

• Allow generating `pub mod` instead of just `mod`

  #222 opened 4 years ago by FranklinChen
  10