Suggestion for these and other areas in the source with TODOs...
# XXX bad.
# XXX (RT#39704) good.
Then it's still obvious if you're in the code that a ticket was opened, and
it's possible to
automate your search for "bad" XXX's (or TODOs).
On Mon Jul 03 23:58:41 2006, mdiep wrote:
>mini:
Kevin Tew wrote:
That would be me!
PRuby is the project.
Suggestions of a better project name are welcome.
Possibly Cardinal? (A ruby-red bird.) The original Cardinal project was
started in 2002, but talking last night we decided it needed a complete
re-write in PGE/TGE (which is when you w
On 7/7/06, Kevin Tew <[EMAIL PROTECTED]> wrote:
Allison Randal wrote:
> I gave a Parrot talk at a Ruby user group meeting tonight. Someone
> mentioned that they had seen somebody on #parrot who was working on a
> new Ruby implementation based on Punie. Do you exist? And is there
> anything we can
# New Ticket Created by "John J. Trammell"
# Please include the string: [perl #39761]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39761 >
Found in docs/pdds/pdd07_codingstd.pod:
All indentation must consist of s
# New Ticket Created by "João Cruz Morais"
# Please include the string: [perl #39759]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39759 >
Given a valid regex (pcre style) as an argument, the script will search inside
any
# New Ticket Created by Jerry Gay
# Please include the string: [perl #39760]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39760 >
compilers\imcc\imcparser.c
imcparser.c
compilers\imcc\imcparser.c(878) : warning C4273: 'ma
I'm unable to hang around Portland after Friday afternoon, I'm sorry to
report, so Saturday hackathoning will miss me. However, I will be arriving
a day _early_ so I'll be in Portland all day Sunday. I understood Patrick
to be in a similar situation, so he might be there Sunday too.
--
Chip Salz
Hi,
Is any one working on Java Script(ECMA-262) implementation in Parrot?
--
Thanks,
Vishal
Allison Randal wrote:
I gave a Parrot talk at a Ruby user group meeting tonight. Someone
mentioned that they had seen somebody on #parrot who was working on a
new Ruby implementation based on Punie. Do you exist? And is there
anything we can do to help you?
Allison
That would be me!
PRuby i
Jerry Gay via RT wrote:
> i've related this ticket to #38887: (Nobody) Result of INFINITY or NAN
> stringification is platform dependent [new]
>
> there are many platforms failing NaN/Inf related tests due to this issue.
That is very true, and very worthy of a separate ticket, but isn't
the failu
On 7/7/06, João Cruz Morais <[EMAIL PROTECTED]> wrote:
Are you talking about the module that has the code to run the steps
from Configure.pl?
Parrot::Config is a module *generated* by Configure.pl, containing
parrot's configuration information in a format (perl module) that's
easy for perl scri
Hi,
I've just submitted the patch.
PS: For future Python scripts a port of the Parrot::Config Perl5 module
would be nice to have.
Are you talking about the module that has the code to run the steps
from Configure.pl?
Regards,
João C Morais
On 7/6/06, via RT John J. Trammell <[EMAIL PROTECTED]> wrote:
Test now uses Parrot::Distribution module instead of mass globbing.
thanks, applied as r13196, with some slight modifications, and additions.
~jerry
João Cruz Morais schrieb:
(moderator please reject my other message - wrong email)
The subject says it all :)
Given a valid regex (pcre) as an argument, the script will search
inside every *.ops file for an opcode name that matches, and dumps
both its arguments and its description. If no argumen
João Cruz Morais schrieb:
(moderator please reject my other message - wrong email)
The subject says it all :)
Given a valid regex (pcre) as an argument, the script will search
inside every *.ops file for an opcode name that matches, and dumps
both its arguments and its description. If no argumen
hcf is actually supposed to explode if possible. Not sure if we should:
1) skip the test usually;
2) close the ticket as "not a bug"
3) eliminate this particular (silly) dynamic opcode.
Regards.
On Jul 7, 2006, at 2:04 AM, Jarkko Hietaniemi (via RT) wrote:
# New Ticket Created by Jarkko Hiet
Thanks, applied as r13195
On Jul 6, 2006, at 5:17 PM, John J. Trammell (via RT) wrote:
"John J. Trammell"
--
Will "Coke" Coleda
[EMAIL PROTECTED]
# New Ticket Created by Chris Dolan
# Please include the string: [perl #39743]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39743 >
This patch changes the main Parrot mailing list address from perl6-
internals to parrot-
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #39752]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39752 >
(dbx) run --gc-debug t/pmc/lexicals_27.pir
# Failed test (t/op/lexicals.t at l
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #39751]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39751 >
(dbx) run --gc-debug t/dynoplibs/myops_4.pir
neither here
thread 0x3 signal Segment
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #39755]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39755 >
t/pmc/complexok 32/53
# Failed test (t/pmc/complex.t at
# New Ticket Created by Chip Salzenberg
# Please include the string: [perl #39744]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39744 >
Keyed access to exception objects should be very forgiving of mistakes,
returning the
# New Ticket Created by Chris Dolan
# Please include the string: [perl #39740]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39740 >
This trivial patch corrects a pair confusing stderr diagnostics from
the bind() and lis
# New Ticket Created by Will Coleda
# Please include the string: [perl #39742]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39742 >
The development version of parrot should not be detecting or
interacting with the insta
Matt Diephouse wrote:
So for the runtime (this is the HLL runtime, not the PIR runtime, btw)
we're all set. Arrays fill the need perfectly and let us access the
root HLL namespace. That makes me think that we don't need any new
opcodes.
Chip's latest simplification eliminates the need for crea
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #39750]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39750 >
(dbx) run --gc-debug t/examples/japh_12.pasm
Parrot VM: PANIC: Out of bound registe
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #39753]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39753 >
(dbx) run --gc-debug t/pmc/io_1.pir
Undef ok 1
Undef ok 2
Assertion failed: (unsign
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #39756]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39756 >
(dbx) run --gc-debug t/examples/japh_10.pasm
run --gc-debug t/examples/japh_10.pasm
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #39754]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39754 >
(dbx) run --gc-debug t/pmc/resizablebooleanarray_20.pasm
thread 0x3 signal Segmenta
# New Ticket Created by "John J. Trammell"
# Please include the string: [perl #39745]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39745 >
Test now uses Parrot::Distribution module instead of mass globbing.
output of dif
Is this bug still reproducible this even after removing everything
Parrot-related from /usr/local? (Also /usr/bin and /usr/lib if you
happen to have installed e.g. Debian's parrot packages.)
# New Ticket Created by "John J. Trammell"
# Please include the string: [perl #39746]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39746 >
New "technical debt" test to look for FIXME, TODO, and XXX markers in
C code and h
I gave a Parrot talk at a Ruby user group meeting tonight. Someone
mentioned that they had seen somebody on #parrot who was working on a
new Ruby implementation based on Punie. Do you exist? And is there
anything we can do to help you?
Allison
Chip Salzenberg wrote:
Well, I see a lot to like about this, but (and you knew there was a "but"
("but" that's my job now :-))), in descending order of difficulty:
And you do it so well. Thank you. :)
* The division into two categories ("global" and "symbol") leaves the third
category (c
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39757]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39757 >
mini:~/Projects/parrot mdiep$ cat test.pir
.sub main :main
$P0 = new .Resiz
35 matches
Mail list logo
