problem testing non-core PIR libraries with Parrot::Test

I've been developing the tree transformation stuff outside the parrot repository, and ran into some problems writing tests for my PIR libraries. After talking to Chip & Patrick, I'll be moving my code into the parrot repository anyway, which scratches my immediate itch. But, long-term it's

Re: [perl #37619] [PATCH] punie patches

On Nov 5, 2005, at 19:37, Will Coleda (via RT) wrote: Sending as a patch since 1) we're close to a freeze, and 2) this is allison's code. Allison: this patch fixes a dependency issue in the makefile, eliminates some deprecation issues, and corrects a small issue in the grammar that allows punie

blocked mime types

> No, it isn't. =) > > The mail list strips out .t attachments (Robert? is this necessary?) We don't strip .t We strip troff attachments. Really, it's a bad mailer that is labeling the .t file a troff mime-type. I've removed the troff types from the bad mime list. -R

[perl #37619] [PATCH] punie patches

# New Ticket Created by Will Coleda # Please include the string: [perl #37619] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=37619 > Sending as a patch since 1) we're close to a freeze, and 2) this is allison's code. A

[perl #37618] [BUG] PAST compiler borked?

# New Ticket Created by Will Coleda # Please include the string: [perl #37618] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=37618 > Trying to patch punie, I get to a point with the following: wcoleda$ cat foo.pir .sub m

[perl #37617] GC bugs, tickled by partcl

# New Ticket Created by Will Coleda # Please include the string: [perl #37617] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=37617 > There are a few GC-related errors occuring in partcl at the moment. This gives a bus e

Re: [perl #37577] [PATCH] Fix a couple of minor niggles (-1 -> uint, K&R prototype)

On 11/5/05, Joshua Hoblitt via RT <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] - Tue Nov 01 04:52:22 2005]: > > > > This patch fixes two classes of issue. > > > > * Don't assign -1 to an unsigned variable; use ~0U instead as it > > makes it clear that the value is intended to be out-of-band (

Re: This week's summary

On Fri, 4 Nov 2005, The Perl 6 Summarizer wrote: Slightly tangentially to this, Dan Sugalski blogged a couple of weeks ago about his successes and failures with Parrot. The comments are worth reading -- there's a fair few more or less well founded complaints about the way the Perl 6

[perl #37577] [PATCH] Fix a couple of minor niggles (-1 -> uint, K&R prototype)

> [EMAIL PROTECTED] - Tue Nov 01 04:52:22 2005]: > > This patch fixes two classes of issue. > > * Don't assign -1 to an unsigned variable; use ~0U instead as it > makes it clear that the value is intended to be out-of-band (g++ > warned about this, and C compilers will increasingly) > > * Ch

Re: suspend and resume opcode

On Nov 5, 2005, at 9:48, Tomo wrote: The usage is following: 1. The parent interpreter creates child a ParrotInterpreter object. 2. The parent interpreter runs the child interpreter with runinterp opcode. 3. The child interpreter suspends by itself with suspend opcode. 4. The parent interpre

r9798: 'make test' results for msvc on win32

Failed Test Stat Wstat Total Fail Failed List of Failed --- t\examples\pasm.t 1 256 61 16.67% 5 t\examples\pir.t 1 256101 10.00% 10 t\library\json_parser.t1 256

Re: suspend and resume opcode

Hello. >> I enjoy Parrot and tried to write new two opcodes -- suspend and resume. >> suspend opcode is to halt interpreter and resume opcode is to restart >> interpreter from where it suspended. > Hmm. How does the C opcode execute, when the runloop was left? > No test case there. What would be t