Re: Rules for method resolution?

2004-02-16 Thread TOGoS
Dunno why it is, but I tried to post a message about 30 hours ago and nothing ever showed up in the NNTP archive. So I re-subscribed again figuring that'd speed things up. You should see my perl box: ... WELCOME to [EMAIL PROTECTED] confirm subscribe to [EMAIL PROTECTED] GOODBYE from [EMAI

Re: Rules for method resolution?

2004-02-16 Thread Dan Sugalski
At 10:12 AM -0500 2/15/04, Michal Wallace wrote: On Sun, 15 Feb 2004, Luke Palmer wrote: > But I think findmethod is a good idea, cross-language-wise. Each language has a different idea of what a method is, and they can store it that way. As long as findmethod is vtableable, you can hook it u

Re: Rules for method resolution?

2004-02-16 Thread Dan Sugalski
At 11:50 PM -0500 2/14/04, Michal Wallace wrote: Maybe for python, findmethod and getprop (or whatever the new eqivalent is) are the same... But I'd suspect that getprop is all any (working) python compiler will use. I've chopped out everything but this bit, since it's perfectly valid, and I think

Re: Rules for method resolution?

2004-02-15 Thread Michal Wallace
On Sun, 15 Feb 2004, Luke Palmer wrote: > As with Perl 6. A sub object has a C trait which specifies what > to do when it's called. Cool. > But I think findmethod is a good idea, cross-language-wise. Each > language has a different idea of what a method is, and they can > store it that way. A

Re: Rules for method resolution?

2004-02-14 Thread Luke Palmer
Michal Wallace writes: > On Fri, 13 Feb 2004, Dan Sugalski wrote: > > > We also have to have a way to fetch the method PMC for a named method > > for later use, which is where the interesting bits come in. > > > > This is required for a number of reasons, including Python, so we > > have to have i

Re: Rules for method resolution?

2004-02-14 Thread Michal Wallace
On Sat, 14 Feb 2004, Michal Wallace wrote: > class Alice: > def whoami(self): > return "Alice" > class Bruce: > def whoami(self): > return "Bruce" > > a = Alice() > b = Bruce() > > a.whoami, b.whoami = b.whoami, a.whoami > assert a.wh

Re: Rules for method resolution?

2004-02-14 Thread Michal Wallace
On Fri, 13 Feb 2004, Dan Sugalski wrote: > We also have to have a way to fetch the method PMC for a named method > for later use, which is where the interesting bits come in. > > This is required for a number of reasons, including Python, so we > have to have it. The question is... *When* is the n

RE: Rules for method resolution?

2004-02-13 Thread Dan Sugalski
At 12:32 PM -0500 2/13/04, Gay, Jerry wrote: > We also have to have a way to fetch the method PMC for a named method for later use, which is where the interesting bits come in. This is required for a number of reasons, including Python, so we have to have it. The question is... *When* is the n

RE: Rules for method resolution?

2004-02-13 Thread Gay, Jerry
> We also have to have a way to fetch the method PMC for a named method > for later use, which is where the interesting bits come in. > > This is required for a number of reasons, including Python, so we > have to have it. The question is... *When* is the name resolved? That > is, if we do: >

Re: Rules for method resolution?

2004-02-13 Thread Dan Sugalski
At 11:38 AM -0500 2/13/04, Dan Sugalski wrote: which calls the named method on the object in the object slot, does all the funky lookups and whatnot, and slams the method PMC into the . That sentence should end "into the appropriate register." -- Dan --