Parrot Bug Summary

2007-06-18 Thread Parrot Bug Summary
Parrot Bug Summary http://rt.perl.org/rt3/NoAuth/parrot/Overview.html Generated at Mon Jun 18 13:00:02 2007 GMT --- * Numbers * New Issues * Overview of Open Issues * Ticket Status By Version * Requestors with

Re: [perl #39197] [RESOLVED] [CAGE] lib/Parrot/Test.pm ignores core dumps

2007-06-18 Thread Andy Dougherty
I'm sorry to report it, but this one isn't fixed. For example, consider test t/src_hash_6. If I compile and run it manually, I get $ t/src/hash_6 42 Segmentation Fault(coredump) But if I run it via the test harness, I get $ perl5.8 -Ilib t/src/hash.t

Perl 6 Parrot Essentials as project documentation

2007-06-18 Thread Allison Randal
I just signed an agreement with O'Reilly that assigns the full copyright in the book Perl 6 and Parrot Essentials to The Perl Foundation. The text is out-of-date, but can be updated much more rapidly than it can be rewritten from scratch. I'll check the Parrot parts into:

Re: [perl #39197] [RESOLVED] [CAGE] lib/Parrot/Test.pm ignores core dumps

2007-06-18 Thread Allison Randal
Andy Dougherty wrote: I think the exit code stuff has been changed (this test used to get reported as failing) but the $builder-diag weirdness is unchanged. Okay, thanks! We'll work on it some more for the next release. Allison

Re: [svn:parrot] r19088 - trunk/src/pmc

2007-06-18 Thread chromatic
On Monday 18 June 2007 12:35:53 [EMAIL PROTECTED] wrote: Log: is_equal is a good const parm Modified: trunk/src/pmc/sub.pmc Does this compile for you? I don't think the PMC to C translator picks up the const here. ./src/pmc/sub.pmc:420: error: conflicting types for ‘Parrot_Sub_is_equal’

Re: [perl #39197] [RESOLVED] [CAGE] lib/Parrot/Test.pm ignores core dumps

2007-06-18 Thread chromatic
On Monday 18 June 2007 09:54:01 Andy Dougherty wrote: I'm sorry to report it, but this one isn't fixed. For example, consider test t/src_hash_6. If I compile and run it manually, I get $ t/src/hash_6 42 Segmentation Fault(coredump) But if I run it via the test harness, I get

[perl #43241] [PATCH] [CAGE] include/parrot/string.h typedefs STRING and String are redundant

2007-06-18 Thread via RT
# New Ticket Created by Mark Glines # Please include the string: [perl #43241] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43241 include/parrot/string.h contains 2 typedefs for the same thing: STRING and String.

Re: [perl #43241] [PATCH] [CAGE] include/parrot/string.h typedefs STRING and String are redundant

2007-06-18 Thread chromatic
On Monday 18 June 2007 09:28:13 Mark Glines wrote: include/parrot/string.h contains 2 typedefs for the same thing: STRING and String. STRING is used everywhere; String is used occasionally. they are interchangeable. This confused me at first, because I thought String was the String PMC, not

Re: [svn:parrot] r19088 - trunk/src/pmc

2007-06-18 Thread Andy Lester
On Jun 18, 2007, at 3:38 PM, chromatic wrote: Does this compile for you? I don't think the PMC to C translator picks up the const here. Sorry, my bad. I modified an autogenerated header file. :-( -- Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance

memcpy

2007-06-18 Thread Andy Lester
Is there a reason we use memcpy( dest, src, sizeof(FOO) ); instead of *dest = *src; The latter should be the exact same code, but be much less likely to be screwed up. At the very least we should be using: memcpy( dest, src, sizeof(*dest) ); Of course, I'm only talking about when

Re: [perl #43241] [PATCH] [CAGE] include/parrot/string.h typedefs STRING and String are redundant

2007-06-18 Thread Andy Lester
On Jun 18, 2007, at 11:28 AM, Mark Glines (via RT) wrote: Here's a patch to consolidate that, and standardize on STRING (based on the fact that it's used *much* more often than String is). And also isn't String a standard C++ class? I've applied your patch. Thanks. -- Andy Lester = [EMAIL

[perl #43245] t/op/bitwise.t #27 Fails with JIT

2007-06-18 Thread via RT
# New Ticket Created by chromatic # Please include the string: [perl #43245] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43245 r19067 needs a bit more work (pardon the pun) to work with parrot -j. Bob, do you

[perl #43165] [TODO] replace dual Artistic/GPL license with Artistic 2.0 only

2007-06-18 Thread Allison Randal via RT
Resolved in r19096.

[perl #43007] [PATCH] docs/configure/files.pod contributed in 'reconfigure' branch

2007-06-18 Thread James Keenan via RT
Well, no one else contributed anything to this file, so there's no point in considering it for trunk. I'll leave it in 'reconfigure' and update it from time to time. kid51

[perl #43085] [PATCH] Parrot::OpsFile::read_ops(): Can we refactor the setting of VERSION

2007-06-18 Thread James Keenan via RT
On Wed May 30 19:30:39 2007, jkeen !-- x -- at verizon.net wrote: [snip] In other words, no src/ops/.ops file currently sets VERSION in any way other than by assignment from PARROT_VERSION. I therefore ask: Why should we not stipulate that 'VERSION = PARROT_VERSION' is the *sole*

Re: [perl #43085] [PATCH] Parrot::OpsFile::read_ops(): Can we refactor the setting of VERSION

2007-06-18 Thread Allison Randal
James Keenan via RT wrote: I therefore ask: Why should we not stipulate that 'VERSION = PARROT_VERSION' is the *sole* way to set VERSION in an .ops file? In that case, (a) we could eliminate the aforementioned 'if' stanza in Parrot::OpsFile::read_ops() and (b) we could probably get away

Cage Cleaners and Patch Monsters

2007-06-18 Thread Allison Randal
I've added lists of names to RESPONSIBLE_PARTIES based on work that people are already doing. If your name has been added, you can take a look at docs/roles_responsibilities.pod to see if you want to accept the responsibility. If I missed your name and it should have been added, drop me a

[perl #43085] [PATCH] Parrot::OpsFile::read_ops(): Can we refactor the setting of VERSION

2007-06-18 Thread James Keenan via RT
Okay, then I won't need to supply a patch. Closing ticket.

[perl #43246] [CAGE] Replace string_from_const_cstring() with string_from_cstring()

2007-06-18 Thread via RT
# New Ticket Created by chromatic # Please include the string: [perl #43246] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43246 Per the note in src/string.c around line 509: /* XXX This is identical to

0.4.13 Release Code Slush

2007-06-18 Thread Allison Randal
With the next release roughly a day away, please refrain from making any major changes in trunk. If you have major changes, hold on to them, create a branch, or create a [PATCH] ticket. Generally, just keep the release in mind while making any commits. Any bug fixes or changes to HLLs or

Re: Perl 6 Parrot Essentials as project documentation

2007-06-18 Thread Moritz Lenz
Allison Randal wrote: I just signed an agreement with O'Reilly that assigns the full copyright in the book Perl 6 and Parrot Essentials to The Perl Foundation. The text is out-of-date, but can be updated much more rapidly than it can be rewritten from scratch. Sounds great. Does TPF have a

Re: 0.4.13 Release Code Slush

2007-06-18 Thread Andy Lester
On Jun 18, 2007, at 6:59 PM, Allison Randal wrote: With the next release roughly a day away, please refrain from making any major changes in trunk. If you have major changes, hold on to them, create a branch, or create a [PATCH] ticket. Generally, just keep the release in mind while making any

[perl #43245] t/op/bitwise.t #27 Fails with JIT

2007-06-18 Thread Bob Rogers
From: chromatic (via RT) [EMAIL PROTECTED] Date: Mon, 18 Jun 2007 15:13:15 -0700 # New Ticket Created by chromatic # Please include the string: [perl #43245] # in the subject line of all future correspondence about this issue. # URL:

Re: 0.4.13 Release Code Slush

2007-06-18 Thread Allison Randal
Andy Lester wrote: When you write up the notes, can you please include a bullet about my compiler work? Will do. And anyone else with NEWS items, drop me a note. I'm reviewing commits and posts tonight to compile the list. Allison

Re: 0.4.13 Release Code Slush

2007-06-18 Thread Allison Randal
Allison Randal wrote: I'm reviewing commits and posts tonight to compile the list. On that note: we've had more than 1400 commits since last month's release. Quite a healthy velocity. :) Allison