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

Showing content from https://mail.python.org/pipermail/python-dev/2008-May/079548.html below:

How should we deal with constant values?

• Previous message: [Python-Dev] Optimization of Python ASTs: How should we deal with constant values?
• Next message: [Python-Dev] Summary of Tracker Issues
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, May 2, 2008 at 10:21 AM, Thomas Lee <tom at vector-seven.com> wrote:
> Any Jython folk care to weigh in on this? If there are no major objections I
> think I'm going to forge ahead with an independant Const() node.
I suspect that having a marker for non-int non-str constants could
also be used for some optimization of Jython bytecode emissions as
well, though of course it would depend on the details.  If the path
from raw AST to optimized AST isn't too crazy Jython can just grow the
same logic.  We have really good AST comparison tests these days, so I
bet it won't be a huge problem for us when the time comes.

-Frank

• Previous message: [Python-Dev] Optimization of Python ASTs: How should we deal with constant values?
• Next message: [Python-Dev] Summary of Tracker Issues
• 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