Use `leex` and/or `yacc`?

[toraritte]

Probably an overkill, but it would definitely be more robust.

http://erlang.org/doc/man/leex.html (Parse tools ref manual; yecc is also treated here)

https://stackoverflow.com/questions/1189684/what-is-the-difference-between-lex-and-yacc https://stackoverflow.com/questions/34618531/how-to-create-a-parser-in-erlang -> http://www.slideshare.net/hamidreza-s/create-your-own-language

https://cameronp.svbtle.com/how-to-use-leex-and-yecc https://andrealeopardi.com/posts/tokenizing-and-parsing-in-elixir-using-leex-and-yecc/ https://arifishaq.wordpress.com/2014/01/22/playing-with-leex-and-yeec/ https://elixirforum.com/t/erlang-elixir-and-leex/11399 http://blog.rusty.io/2011/02/08/leex-and-yecc/ http://arjanvandergaag.nl/blog/write-your-own-parser.html https://notes.eellson.com/2017/01/22/html-parsing-in-elixir-with-leex-and-yecc/

http://erlang.org/pipermail/erlang-questions/2010-March/050035.html -> https://github.com/marianoguerra/efene -> https://github.com/marianoguerra/match

General: http://web.mit.edu/6.005/www/fa15/classes/18-parser-generators/

[toraritte]

The current Erlang nixpkgs do not seem to include leex/yecc.

1. Make minimum viable program (i.e., do parsing any way possible).
2. Build Erlang from source with all possible options.
3. Figure out how to include leex/yacc if still not available. (This would probably be a good starting point, but code is almost 10 years old.)