"Phillip J. Eby" <[EMAIL PROTECTED]> writes:
> At 10:47 AM 10/24/2008 +0200, J. Sievers wrote:
>> - Right now, CPython's bytecode is translated to direct threaded code
>> lazily (when a code object is first evaluated). This would have to
>> be merged into compile.c in some way plus some assorte
[EMAIL PROTECTED] writes:
> Guido> This is very interesting (at this point I'm just lurking), but
> Guido> has anyone pointed out yet that there already is something else
> Guido> called VPython, which has a long standing "right" to the name?
>
> I believe Jakob has already been notifi
[EMAIL PROTECTED] writes:
> BTW, as to the implementation of individual VM instructions I don't believe
> the Vmgen stuff affects that. It's just the way the instructions are
> assembled.
Vmgen handles the pushing and popping as well. E.g. ROT_THREE becomes:
rot_three ( a1 a2 a3 -- a3 a1 a2 )
I added a page to wiki.python.org:
http://wiki.python.org/moin/CPythonVmInternals
This incorporates most of Martin v. Löwis's additions (except for a
few bits which
I need to look into more).
In any case, thanks for the feedback!
Cheers,
-jakob
___
Py
Hi,
I've been reading the Python VM sources over the last few afternoons and
I took some notes, which I thought I'd share (and if anyone familiar
with the VM internals could have a quick look at them, I'd really
appreciate it).
Cheers,
-jakob
Unless otherwise noted, the source file in question i
