TAKASE Ryo (loloicci) comments

Results 27 comments of


                                            TAKASE Ryo (loloicci)

Parser does not work when compiling to JavaScript

Sorry, nimly does not support compiling to JS now. nimly targets to use as a part of compilers, so it only targets C/C++ compiling. In what situation do you want...

Ability to define two parsers from the same lexer

@fish-face Thank you for the reporting! I won't fix this, but maybe I can help you. `nimy` is designed as a macro to make the parsing table and **define the...

nimly Uses Too Many Loops In Compile-time

You can avoid this error to use the new compiler option maxLoopIterationsVM:N (maybe later than Nim v1.0.6) (See also https://nim-lang.org/docs/nimc.html). Before v1.0.6, you can use niml with compiler build with...

nimly Uses Too Many Loops In Compile-time

improve some #25

nimly Uses Too Many Loops In Compile-time

It maybe solved when nim becomes version 1.0.0.

nimly Uses Too Many Loops In Compile-time

@samdmarshall thanks for your reporting. Could you share the code with the bug if you can?

nimly Uses Too Many Loops In Compile-time

Thanks! Either is fine. Link to #11 if you post as a new issue.

nimly Uses Too Many Loops In Compile-time

@bung87 Thank you for your analysis! > if toSeq(sTran.keys) == toSeq(tran.keys): I modify to this , reduce the iterations, it seems under the compare calls the argument changes dynamically. If...

nimly Uses Too Many Loops In Compile-time

Sorry, @bung87. Your suggestion does not work expectedly. > toSeq(sTran.keys) == toSeq(tran.keys) This returns always true and causes error in `nimble test`. (`nim c -r tests/test_lexgen.nim` provides more information) I...

nimly Uses Too Many Loops In Compile-time

@bung87 > write a wrong grammar also will cause this? No (as far as I know). This error is caused when the calculation needed to generate the lexer is too...