bug in ASTNode#each about rltk HOT 8 CLOSED

Fixed this issue. Thanks for including the test case.

May I ask what you are using RLTK for? It helps me prioritize my work if I know how people are using it.

from rltk.

I'm trying to do a coffeescript style alternative syntax for go (although this is mostly for testing parsing frameworks)

from rltk.

How are you finding RLTK so far? Are there any features that you have found in other frameworks that you really like and RLTK doesn't have? Have you tried the parse tree printing functionality yet?

from rltk.

I was quite frustrated with all those LALR (or even worse LL(k)) parser generators and my inability to thing of grammars in terms of lookahead sets and how to build my grammar around the parsergenerator. So GLR is really refreshing.

By "parse tree printing functionality" you mean the dot file output I guess? It helped me to figure out what was going on in the other "duplicated entries" bug.

What I would really like was a way to say "this is a dead end - don't even try" in the code part of the rules. This way one could use the handleing of ambiguity to perform lexical scoping in the parser (think a "variable_read" rule that "fails" if the variable is not in the scope). On the other hand maybe that's exactly what the error productions are used for (didn't understand them yet). Also I find the error reporting to be poor compared to other frameworks (which is mostly ok since I'm mostly just prototyping currently but might be quite a bigger problem if someone wants to use it for code that is used by anyone but themselves). I have not yet used the LLVM part so no comments on that.

cheers and thx for the good work :)

from rltk.

Do you have any examples of good error reporting from other frameworks? Good error reporting is key, and if there is more I could be doing to help developers I'd like to add that functionality.

from rltk.

With regards to error reporting for the developer, I really liked parslet (http://kschiess.github.com/parslet/get-started.html there is an example there). But then, this kind of error reporting is pretty much useless for end users I guess. Regarding error reporing for end user - I really have little experience with that.

from rltk.

RLTK Parsers can print out information about the parsing process by passing the parse method the verbose: true option. It's not quite as nice as the Parslet output, but I'll work on it.

from rltk.

awesome :)

from rltk.