Comments on: 64k tinypy - parsing woes http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/ games, tech, web, stuff, biz, and bilge Wed, 03 Dec 2008 06:49:05 +0000 http://wordpress.org/?v=2.5.1 By: howard http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-765 howard Sat, 26 Jan 2008 10:41:49 +0000 http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-765 Check out PyParsing http://pyparsing.wikispaces.com/ Check out PyParsing
http://pyparsing.wikispaces.com/

]]> By: philhassey http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-762 philhassey Sat, 26 Jan 2008 03:29:00 +0000 http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-762 rh - I'll try and do that next time :) rh - I’ll try and do that next time :)

]]> By: rh http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-761 rh Sat, 26 Jan 2008 02:42:09 +0000 http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-761 Sounds really cool, but is there any chance of seeing a non-svn download? Even a snapshot or something, for those of us stuck behind firewalls where the svn protocol is unavailable. Sounds really cool, but is there any chance of seeing a non-svn download? Even a snapshot or something, for those of us stuck behind firewalls where the svn protocol is unavailable.

]]> By: philhassey http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-739 philhassey Wed, 23 Jan 2008 16:07:54 +0000 http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-739 http://javascript.crockford.com/tdop/index.html was also a helpful resource. http://javascript.crockford.com/tdop/index.html

was also a helpful resource.

]]> By: Kumar McMillan http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-734 Kumar McMillan Tue, 22 Jan 2008 22:17:31 +0000 http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-734 I know it looks like a scary edu tool but I saw a presentation on the aperiot module once and it looked surprisingly easy to use. IIRC it includes a grammar for Python. As far as speed and error reporting, I saw demos and benchmarks that made it look very attractive. It may not be as compact as you like, I don't know about this. http://moncs.cs.mcgill.ca/people/eposse/projects/aperiot/atglance.dtml I know it looks like a scary edu tool but I saw a presentation on the aperiot module once and it looked surprisingly easy to use. IIRC it includes a grammar for Python. As far as speed and error reporting, I saw demos and benchmarks that made it look very attractive. It may not be as compact as you like, I don’t know about this.

http://moncs.cs.mcgill.ca/people/eposse/projects/aperiot/atglance.dtml

]]> By: philhassey http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-733 philhassey Tue, 22 Jan 2008 19:52:46 +0000 http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-733 Ben - sounds interesting, I'll take a look at it :) Ben - sounds interesting, I’ll take a look at it :)

]]> By: Ben http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-732 Ben Tue, 22 Jan 2008 19:41:05 +0000 http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-732 Have a look at this (it's a PDF of about 0.5 MB): _Compiler Construction_ http://www.google.com/search?client=safari&rls=en-us&q=compiler+construction,+niklaus+wirth&ie=UTF-8&oe=UTF-8 Niklaus Wirth is a master of compact, fast and simple recursive decent parsers. His book also has the great virtue of brevity. Sources available too: http://www.cs.inf.ethz.ch/~wirth/books/CompilerConstruction/ Have a look at this (it’s a PDF of about 0.5 MB):

_Compiler Construction_

http://www.google.com/search?client=safari&rls=en-us&q=compiler+construction,+niklaus+wirth&ie=UTF-8&oe=UTF-8

Niklaus Wirth is a master of compact, fast and simple recursive decent parsers. His book also has the great virtue of brevity.

Sources available too:

http://www.cs.inf.ethz.ch/~wirth/books/CompilerConstruction/

]]> By: Allefant http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-731 Allefant Tue, 22 Jan 2008 17:33:33 +0000 http://www.philhassey.com/blog/2008/01/22/64k-tinypy-parsing-woes/#comment-731 I have no idea about LR/LL/whatever either, but the way I did a python-like parser some time ago sort of works like this: Simply look at the first token, then depending on what it is, call a function to handle it. E.g. I see an "if", then I call parse_if(). That now looks again at the first token, and so on. As a special case, I sometimes look ahead. For example: if 1 + 2 > 3: I get to the "1" like: parse_program() -> parse_block() -> parse_statement() -> parse_if() -> parse_expression(). Here, I look ahead to the > before I know that I can already handle the "1 + 2". Anway, no idea if this is an algorithm with a name, to me it's just basically doing it all "manually". My code can be seen here, but I would advice against looking at it, as it's not commented and written in my own pyplus derived language :P http://lland.svn.sourceforge.net/viewvc/lland/landmagic/src/ Anyway, the relevant files would be pyrser.py and expression.py. I have no idea about LR/LL/whatever either, but the way I did a python-like parser some time ago sort of works like this: Simply look at the first token, then depending on what it is, call a function to handle it. E.g. I see an “if”, then I call parse_if(). That now looks again at the first token, and so on. As a special case, I sometimes look ahead. For example:

if 1 + 2 > 3:

I get to the “1″ like: parse_program() -> parse_block() -> parse_statement() -> parse_if() -> parse_expression(). Here, I look ahead to the > before I know that I can already handle the “1 + 2″. Anway, no idea if this is an algorithm with a name, to me it’s just basically doing it all “manually”.

My code can be seen here, but I would advice against looking at it, as it’s not commented and written in my own pyplus derived language :P http://lland.svn.sourceforge.net/viewvc/lland/landmagic/src/
Anyway, the relevant files would be pyrser.py and expression.py.

]]>