[erlang-questions] Debugging yecc grammars: what techniques are available?

[Walter Weinmann]

I've done a project with he OpenCypher <http://opencypher/openCypher>
language: https://github.com/walter-weinmann/ocparse
https://github.com/walter-weinmann/ocparse. This should be a good example
how to apply leex and yecc.

I've done also a second one, but honestly I'm very unhappy with the
limitations of LALR parsing. I'm now in the process to switch to neotoma
<http://seancribbs/neotoma>, which is based on Parser Expression Grammars
and it looks very promising.

Regards

Walter


On 5 February 2017 at 00:45, Hugo Mills <hugo@REDACTED> wrote:

>    I'm in the process of writing a domain-specific language, using a
> custom lexer and a yecc parser. In the process of attempting to add a
> new feature to the grammar, I've managed to break what appears to me
> to be a completely unrelated piece of the grammar: I'm adding a
> structure similar to a list comprehension, and suddenly the integer
> comparison operators have stopped working in one group of cases.
>
>    What approaches are there for debugging this kind of problem? The
> best I can some up with is inspection of the .yrl source in detail,
> but that's not helping. How else can I work out what the issue is?
>
>    Obviously, I could post the grammar here for inspection by more
> experienced minds than mine, but I'd prefer to find better tooling and
> techniques rather than mere appeal to higher authority...
>
>    Hugo.
>
> --
> Hugo Mills             | Strive for apathy!
> hugo@REDACTED carfax.org.uk |
> http://carfax.org.uk/  |
> PGP: E2AB1DE4          |                                      Andrew
> Zalotocky
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>


__________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20170205/42e10b2d/attachment.htm>