Figured I'd drop this note as I'm poking at this over lunch.
There's a number of opcodes that access attributes of the code
object. What I'm going to do is take advantage of the fact that we
stick the sub/method being called into P0, and hang attributes off of
that. I think this'll do what we
On Thu 15 Jul 2004 18:53, Dan Sugalski [EMAIL PROTECTED] wrote:
Figured I'd drop this note as I'm poking at this over lunch.
if you try to pun the piethon spelling,
py-thong
would sound a lot sexier
There's a number of opcodes that access attributes of the code
object. What I'm going to do
At 6:57 PM +0200 7/15/04, H.Merijn Brand wrote:
On Thu 15 Jul 2004 18:53, Dan Sugalski [EMAIL PROTECTED] wrote:
Figured I'd drop this note as I'm poking at this over lunch.
if you try to pun the piethon spelling,
py-thong
would sound a lot sexier
It'll be Guido and I. Are you *sure* that sexier
Dan Sugalski wrote:
Figured I'd drop this note as I'm poking at this over lunch.
There's a number of opcodes that access attributes of the code object.
What I'm going to do is take advantage of the fact that we stick the
sub/method being called into P0, and hang attributes off of that. I
think
At 10:19 PM +0200 7/15/04, Leopold Toetsch wrote:
Dan Sugalski wrote:
Figured I'd drop this note as I'm poking at this over lunch.
There's a number of opcodes that access attributes of the code
object. What I'm going to do is take advantage of the fact that we
stick the sub/method being called
