<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 18, 2012, at 3:30 AM, Nick Coghlan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">- Eugene Toder's patch to add an AST optimisation step to the compiler<br>chain (<a href="http://bugs.python.org/issue11549">http://bugs.python.org/issue11549</a>) (I've asked Eugene about<br>this patch more recently and his current thought is that subsequent<br>improvements to the peephole optimisation have rendered it less<br>valuable. However, the patch is still a potentially useful resource<br>for anyone investigating bytecode optimisation ideas)<br></span></blockquote></div><div><br></div>+1 for furthering Eugene's patch. The AST is the correct place<div>to do some of the optimizations currently done by the peepholer.</div><div><br></div><div><br></div><div>Raymond</div></body></html>