Logged In: YES 
user_id=34209

I'd not be proud in any case; neither the concept nor most
of the implementation was my idea :-) But my questions still
stand; the 3% slowdown in pystone is a lot if all you see is
a 1.5% gain in Zope3 startup time, but I can't think of any
ways to fix that before next friday, or before 2.3 is
released. (The problem is either code size or switch length,
which can be 'fixed' by culling code, re-ordering the switch
again or changing the switch into a computed-goto.) And I'd
need to find me a machine with less cache to actually notice
the slowdown :-)