Hello, I just found about this list!
I'm a software engineer with a good part of my career spent on language theory and programming language implementation. I recently wrote the tool Grako[1], basically because I was hired to deal with Software AG Natural, and COBOL with embedded CICS and SQL, the LLxxx tools I knew made it too hard (I tried), and the PEG parsers around seemed not to be up to thousands of lines of unencumbered grammars. One of the biggest questions I had while building Grako was about how to implement a "cut" feature, much like the one Prolog-style parsers have. It is something I have not seen in other PEG parsers, but that I've tried to implement to my best because I think it is of value. The original question is at SO [2]. I'd be very interested in your opinions. Cheers! [1] https://pypi.python.org/pypi/grako [2] http://goo.gl/AnNbp -- Juancarlo Añez * *
_______________________________________________ PEG mailing list PEG@lists.csail.mit.edu https://lists.csail.mit.edu/mailman/listinfo/peg
