dyoo / ragg Goto Github PK

If a parser's given the empty sequence, we might give a very bad error message from deep within cfg-parser.

We don't have documentation on ragg/codegen/sexp-based-lang

#lang planet dyoo/autogrammar/lalr
foo: "foo"

produces the following error:

grammar.rkt:22:0: parser-non-terminals: foo used as both token and non-terminal in: foo

mye asks: Is there a reason the BNF based syntax doesn't work for submodules? (I'm assuming this is possible with the submodules which it might not)

The major obstacle I see to this is use of "#" for line comments, which might not work nicely with the Racket reader.

soegaard requests some mechanism for communicating values from the parser back to the tokenizer. Probably a trigger based on semantic actions.

#lang ragg
foo   : "start"

.racket/6.11/pkgs/ragg/ragg/cfg-parser/cfg-parser.rkt:710:55: parser-non-terminals: start used as both token and non-terminal in: start

There is no license, so by default, it is proprietary.

In issue #12 you were kind enough to explicitly move ragg under the LGPL to be compatible with Racket.

Racket is about to be relicensed under Apache+MIT.

For this reason, would you consider relicensing ragg under the MIT license, so it can remain maximally compatible with Racket’s licensing? Thanks.