[Python-Dev] Idea for a fast calling convention
Bob Ippolito
bob at redivi.com
Mon Mar 1 07:01:08 EST 2004
On Mar 1, 2004, at 5:52 AM, Michael Hudson wrote:
> Christian Tismer <tismer at stackless.com> writes:
>
>> p.s.: I believe some automatic source analysis and rewrite might pay
>> off in other areas as well. Grepping through the sources, there are
>> still very many similar patterns of PyArg_ParseTupleXXX calls, which
>> could be replaced by less general, optimized versions. This would
>> even *not* cause code bloat, since all those calling sequences would
>> be smaller than now.
>
> Well, yes. C sucks seriously for things like this, though. It's
> frankly embarassing that *every* time, say, ''.split() is called, some
> silly string is being parsed. Unclear what to do about this (excpet
> PyPy, I guess).
Surely there's other reasonable options. For example, we could start
using something like Pyrex that could be modified to generate whatever
gnarly C code needs to happen for optimal runtime performance with
minimal input ugliness :)
-bob
More information about the Python-Dev
mailing list