Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <975cd42a-00b0-4d2e-9f22-95b4021a7fbb@g32g2000pri.googlegroups.com>
References: <0dc26f12-2541-4d41-8678-4fa53f347acf@g9g2000yqb.googlegroups.com> <42e335a7-b872-4229-ae02-13d61b7fab35@w22g2000prj.googlegroups.com> <mailman.658.1314887244.27778.python-list@python.org> <975cd42a-00b0-4d2e-9f22-95b4021a7fbb@g32g2000pri.googlegroups.com>
From: Ian Kelly <ian.g.kelly@gmail.com>
Date: Fri, 2 Sep 2011 14:30:14 -0600
Subject: Re: Why do class methods always need 'self' as the first parameter?
To: John Roth <johnroth1@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.721.1314995446.27778.python-list@python.org>
Lines: 48
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:12674

On Fri, Sep 2, 2011 at 11:51 AM, John Roth <johnroth1@gmail.com> wrote:
>> I don't see how you could get rid of the wrappers. =A0Methods would
>> still need to be bound, somehow, so that code like this will work:
>>
>> methods =3D {}
>> for obj in objs:
>> =A0 =A0 if obj.is_flagged:
>> =A0 =A0 =A0 =A0 methods[obj.user_id] =3D obj.do_work
>> =A0 =A0 else:
>> =A0 =A0 =A0 =A0 methods[obj.user_id] =3D obj.do_other_work
>> # ...
>> methods[some_user_id]()
>>
>> Without method wrappers, how does the interpreter figure out which
>> instance is bound to the method being called?
>>
>> Cheers,
>> Ian
>
> Good question.
>
> Currently the instance wrapper is created during method instantiation,
> so the instance is obviously available at that point. There are two
> rather obvious ways of remembering it. One is to use the invocation
> stack, which has the instance. Another would be for the compiler to
> create a local variable for the instance and possibly the class and
> fill them in at instantiation time. Both of these require fixing the
> names "self" and "cls" so the compiler knows what to do with them. The
> first would require giving these two names their own bytecodes, the
> second makes them simple local variables the same as the ones in the
> method headers. The latter also allows them to be changed by the
> method, which is probably not the world's best programming practice
> although it's possible now.

That's not what I asked.  Both of those options are storing the
instance within a stack frame, once it's been called.  I'm asking how
you would remember the instance during the interval from the time when
the method
is accessed until when it has been called.

In the code above, the method is accessed just before it is stored in
the dictionary.  That is when the method wrapper is currently created,
and the instance is available.  It is not called until much later,
possibly not even within the same function.  How would you remember
the instance over that period without wrapping the function?

Cheers,
Ian