Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/1999-September/000827.html below:

[Python-Dev] Catching "return" and "return expr" at compile time

• Previous message: [Python-Dev] Catching "return" and "return expr" at compile time
• Next message: [Python-Dev] Catching "return" and "return expr" at compile time
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Skip Montanaro writes:
 > thing?  Ideally, I'd like to see a framework that brings the parser module's
 > output up to a level where mere mortals like me can reason about Python

  This was exactly what I wanted to prevent when I created the parser
module!  ;-)
  I think a wrapper that simplifies the parse tree wouldn't be too
hard to do; you simply have to be sure that the simplified version can 
be re-elaborated to pass back to the byte-code compiler via
parser.sequence2ast(<seq>).compile().  Otherwise you can't modify the
tree without loosing line number information, which would be nice to
keep around!


  -Fred

--
Fred L. Drake, Jr.	     <fdrake@acm.org>
Corporation for National Research Initiatives

• Previous message: [Python-Dev] Catching "return" and "return expr" at compile time
• Next message: [Python-Dev] Catching "return" and "return expr" at compile time
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4