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 Thursday 29 November 2007 20:54:13 Will Coleda wrote:
> pynie currently doesn't run:
>
> $ ../../parrot pynie.pbc
> No such attribute 'PGE::OPTable
> current instr.: 'parrot;Pynie::Grammar;onload' pc 117653 (src/parser/
> indent.pir:20)
> called from Sub 'parrot;Pynie::Compiler;main' pc -1 ((un
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
On Nov 28, 2007, at 1:29 AM, Joe Sadusk via RT wrote:
Heh, ok, grammar fixed and resubmitted. And yes, I've tested it on
Linux (Fedora 7) and Windows with MSVC 2005. I don't have a non-glibc
unix to try it out with however.
Joe
On Mon Nov 26 09:50:28 2007, [EMAIL PROTECTED] wrote:
On Sunda
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.
# New Ticket Created by Will Coleda
# Please include the string: [perl #47980]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47980 >
pynie currently doesn't run:
$ ../../parrot pynie.pbc
No such attribute 'PGE::OPTable
cu
# New Ticket Created by Will Coleda
# Please include the string: [perl #47978]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47978 >
On feather, languages/c99 (et al.) fail with:
$ make
../../parrot -o src/CPP_PGE2AST.pbc
On Thu, Nov 29, 2007 at 06:17:57PM -0800, chromatic wrote:
> On Thursday 29 November 2007 18:05:32 Patrick R.Michaud wrote:
>
> > Yes, that subject line is correct -- I've found a bug
> > that shows itself _only_
> >- when I build Parrot using ccache,
> >- for one seemingly obscure json te
On Nov 29, 2007, at 10:34 PM, Will Coleda (via RT) wrote:
from DEPRECATED.pod:
The C opcode is deprecated (replaced by C) and
will be
removed after the 0.5.0 release.
A quick read of PDD17 shows that to replace get_mro, I probably want
the inspect_str vtable, exposed via the inspect_p_p
# New Ticket Created by Will Coleda
# Please include the string: [perl #47976]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47976 >
from DEPRECATED.pod:
The C opcode is deprecated (replaced by C) and will be
removed afte
# New Ticket Created by Will Coleda
# Please include the string: [perl #47974]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47974 >
From PDD17:
=item inspect
PMC* inspect(INTERP, PMC* self)
Return a hash of all cha
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
On Thursday 29 November 2007 18:05:32 Patrick R.Michaud wrote:
> Yes, that subject line is correct -- I've found a bug
> that shows itself _only_
>- when I build Parrot using ccache,
>- for one seemingly obscure json test,
>- when running Parrot with the --gc-debug core (e.g., 'make te
# 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
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #47970]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47970 >
Yes, that subject line is correct -- I've found a bug
that shows itself _only_
Over the past year I've opened several RT tickets to which the response
has been, errr, underwhelming. I'd like to see if I could get any
dialogue going on any of the issues raised in any of them. So here are
links to the issues and a subject line or brief description:
https://rt.perl.org/rt
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #47966]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47966 >
In the list of "Standard Parrot Exceptions" in pdd23, there's
no item given for "e
I should also note that the problem is related to the :outer
somehow, because if we remove :outer from the definition of 'foo'
in x.pir then everything works as expected:
$ ./parrot y.pir
compiler start
reading x.pir into $S0
compiling (but not running) $S0
XYZ::BEGIN
done
On Wed, Nov 28, 2007 at 11:22:30AM -0800, James Fuller wrote:
> # New Ticket Created by "James Fuller"
> # Please include the string: [perl #47926]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=47926 >
>
>
> after buil
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #47956]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47956 >
This is a long one to explain, but it's another example showing
some difficulties
20 matches
Mail list logo
