pyPEG 0.27 and YML 2.0.27
... because unfortunately the fix before triggered a new bug. So testing, bughunting, testing was necessary. Now it should be enough ;-)
Fixed a problem with line numbers in syntax errors
... so I updated pyPEG to 0.26 and YML to 2.0.26.
pyPEG is now thread-safe
... the two parsing functions are now reentrant.
You can find pyPEG at the pyPEG homepage as usual.
pyPEG updated to 0.24
pyPEG does a good job already in finding syntax errors and assigning them to the right line.
But pyPEG only is a parser - of course, you'll write a backend reading pyAST, if you're using pyPEG. And then you may want to assign line numbers in the source file to errors and warnings, too, which you're generating. For that case you need to know which object in the pyAST is where in the source text.
For that case, there now is the functionality to optionally attach a character number to each parsed symbol into the pyAST. The parse() and the parseLine() functions have just one parameter more now.
You can find the newest version on the pyPEG homepage
pyPEG released
Because it may be of use for other Python projects, too, I released my pyPEG parser-interpreter.
If you need a general parser for context free languages as a small Python module, you may use it.
YML 2.0 released
I wrote a PEG parser-interpreter implementation for my YPL project. I wanted to test it out.
For that case, I needed a sample application. My language YML didn't use a parser yet (I heavily depended on the Python parser).
So I decided to reimplement YML using my own parser. The result you can find on the YML Homepage, as usually.
YML 2 is not completely syntax compatible with YML 1 for good reasons. You can find support for YML 1.x here.
Skandal: Bernd das Brot entführt!
Was soll jetzt nur aus dem armen Bernd werden?
Happy New Year...
... to all of you! ;-)
