[perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2008-03-16 Thread James Keenan via RT
On Wed May 16 04:27:03 2007, [EMAIL PROTECTED] wrote: > The results of my first post in this thread were probably caused by > the fact that some files were not updated correctly (I am new to > revision control). Both Allison's and Alek's patches have in fact the > same effect. > > But the problem

Re: [perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2007-05-16 Thread Mehmet Yavuz Selim Soyturk
The results of my first post in this thread were probably caused by the fact that some files were not updated correctly (I am new to revision control). Both Allison's and Alek's patches have in fact the same effect. But the problem that I stated in my second post and the proposed solution are val

Re: [perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2007-05-15 Thread Mehmet Yavuz Selim Soyturk
On 5/15/07, Alek Storm <[EMAIL PROTECTED]> wrote: On 5/14/07, Mehmet Yavuz Selim Soyturk <[EMAIL PROTECTED] > wrote: > Should we not be able to use an object that implements 'invoke' as a > method of another object? There is some strange behaviour when I try > to. I see what you're saying, and i

Re: [perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2007-05-15 Thread Alek Storm
On 5/15/07, Allison Randal via RT <[EMAIL PROTECTED]> wrote: And reverted in r18541. The patch is fragile. Broken on Windows, and fixing it for Windows breaks it for OSX and Linux. Whoops, I had no idea it didn't work on Windows. I have no way to test on that platform. What was the problem?

Re: [perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2007-05-15 Thread Alek Storm
On 5/14/07, Mehmet Yavuz Selim Soyturk <[EMAIL PROTECTED] > wrote: Should we not be able to use an object that implements 'invoke' as a method of another object? There is some strange behaviour when I try to. I see what you're saying, and it looks like you want a functor. We can't do exactly

[perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2007-05-14 Thread Allison Randal via RT
And reverted in r18541. The patch is fragile. Broken on Windows, and fixing it for Windows breaks it for OSX and Linux. Allison

Re: [perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2007-05-14 Thread Mehmet Yavuz Selim Soyturk
On 5/10/07, via RT Alek Storm <[EMAIL PROTECTED]> wrote: # New Ticket Created by "Alek Storm" # Please include the string: [perl #42919] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=42919 > Because PIR can't tell the diff

[perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2007-05-14 Thread Allison Randal via RT
Thanks, applied in r18535 with some modifications. Particularly, changed the name of the flag from PARROT_ARG_OBJECT to PARROT_ARG_INVOCANT, moved the code for handling object overrides of 'invoke' from delegate.pmc to parrotobject.pmc, and kept the regression test for RT #41732 (still relevant, it

[perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed

2007-05-11 Thread Alek Storm
# New Ticket Created by "Alek Storm" # Please include the string: [perl #42919] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=42919 > Because PIR can't tell the difference between invoking an object PMC and invoking a sub