On Tue, Aug 12, 2008 at 02:14:07PM +0200, Allison Randal wrote:
> Will Coleda wrote:
>> I agree that any removed feature should have a deprecation cycle;
>> Here's my pitch for how we've already done that; the list of
>> deprecated features has RTs; the RT listed what was going to have to
>> happen
Will Coleda wrote:
I agree that any removed feature should have a deprecation cycle;
Here's my pitch for how we've already done that; the list of
deprecated features has RTs; the RT listed what was going to have to
happen for some time now; This covers us on the deprecation
notification.
I am w
On Tue, Aug 12, 2008 at 2:39 AM, Patrick R. Michaud via RT
<[EMAIL PROTECTED]> wrote:
> On Mon Aug 11 18:10:30 2008, coke wrote:
>>
>> 'getclass' is dead, patch applied in r30176. All tests pass.
>
> r30176 (and it's subsequent fix for builtins.h in r30179) cause Rakudo
> to stop building with:
>
>
On Mon Aug 11 18:10:30 2008, coke wrote:
>
> 'getclass' is dead, patch applied in r30176. All tests pass.
r30176 (and it's subsequent fix for builtins.h in r30179) cause Rakudo
to stop building with:
../../parrot -o perl6.pbc perl6.pir
error:imcc:The opcode 'exp_p_p' (exp<2>) was not found. Che
On Tue Aug 05 09:10:58 2008, coke wrote:
> On Tue Jul 01 18:56:40 2008, coke wrote:
> > On Thu Nov 29 22:08:11 2007, [EMAIL PROTECTED] wrote:
> > > Will Coleda wrote:
> > > >
> > > > 1) using getclass (aka, reject this ticket)
> > > > 2) doing something custom for the say method here (like, say,
>
On Tue Jul 01 18:56:40 2008, coke wrote:
> On Thu Nov 29 22:08:11 2007, [EMAIL PROTECTED] wrote:
> > Will Coleda wrote:
> > >
> > > 1) using getclass (aka, reject this ticket)
> > > 2) doing something custom for the say method here (like, say,
> > > translating say 'what' into something like "getst
On Thu Nov 29 22:08:11 2007, [EMAIL PROTECTED] wrote:
> Will Coleda wrote:
> >
> > 1) using getclass (aka, reject this ticket)
> > 2) doing something custom for the say method here (like, say,
> > translating say 'what' into something like "getstdout P0;
> > P0.'say'('what');"
> > 3) eliminating
Patrick R. Michaud wrote:
The problem isn't so much with ParrotIO as it is with the way that
'say' is implemented. Say expects to be able to get the ParrotIO
class object and invoke the 'say' method on it -- but this is no
longer valid under pdd15 objects, where the class methods are no
longe
On Thursday 29 November 2007 22:07:30 Allison Randal wrote:
> I'm in favor of making 'say' a standard opcode, whatever else we do.
> That is, assuming it's worth keeping. Show of hands if you use it and
> want to keep it.
I made it work on all four register types recently. I'm all for it.
-- c
On Fri, Nov 30, 2007 at 08:07:30AM +0200, Allison Randal wrote:
> Will Coleda wrote:
> >1) using getclass (aka, reject this ticket)
> >2) doing something custom for the say method here (like, say,
> >translating say 'what' into something like "getstdout P0;
> >P0.'say'('what');"
> >3) eliminating
Will Coleda wrote:
1) using getclass (aka, reject this ticket)
2) doing something custom for the say method here (like, say,
translating say 'what' into something like "getstdout P0;
P0.'say'('what');"
3) eliminating the automagic method translation used here and just
writing a 'say' opcode.
On Nov 29, 2007, at 9:17 PM, Will Coleda (via RT) wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #47972]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47972 >
From DEPRECATED.pod:
The C o
# New Ticket Created by Will Coleda
# Please include the string: [perl #47972]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47972 >
From DEPRECATED.pod:
The C opcode is deprecated (replaced by the C
opcode) and
will b
13 matches
Mail list logo
