RetroSearch Browse

Tue Feb 10 18:16:23 CET 2009 · https://mail.python.org/pipermail/python-dev/2009-February/085968.html

Daniel Stutzbach wrote:
> On Tue, Feb 10, 2009 at 10:24 AM, Cesare Di Mauro
> <cesare.dimauro at a-tono.com <mailto:cesare.dimauro at a-tono.com>> wrote:
> 
>     Could it be applyable to other operations as well? So, if I wrote:
>      c = not(a < b)
>     the compiler and/or peephole optimizer can generate bytecodes
>     instructions which, instead, execute the following operation:
>      c = a >= b
> 
> 
> Those two expressions are equivalent for integers, but not necessarily
> equivalent for objects that define their own comparison operator.
> 
That's true, but the same *could* be said about the existing
optimizations for objects that define their own __contains__.

regards
 Steve
-- 
Steve Holden        +1 571 484 6266   +1 800 494 3119
Holden Web LLC              http://www.holdenweb.com/

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

Showing content from https://mail.python.org/pipermail/python-dev/2009-February/085968.html below:

[Python-Dev] Expression optimizations