[perl #60178] Commit r32189 breaks Parrot on Mac OS X 10.5.4

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #60178] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=60178 > I'm running Mac OS X 10.5.4, and can't compile Parrot >r32189. I managed to compile the

[perl #60166] [BUG] Exception handling in parrot doesn't unwind stack.

This example fails because the op find_method uses Parrot_ex_throw_from_c_args, that handles the exception in an inner runloop. From an opcode is better to use Parrot_ex_throw_from_op, wich jumps to the handler in the current runloop. I'm working on a patch that defines the helper function Parrot_

[perl #60186] [PATCH] make PGE support {PIR} closures instead of just {{PIR}}

# New Ticket Created by Chris Dolan # Please include the string: [perl #60186] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=60186 > As of parrot rev 32120, PGE only supports the old S05 closure syntax that had double cu

[perl #60182] pirc/new codetest failures

# New Ticket Created by Moritz Lenz # Please include the string: [perl #60182] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=60182 > r32205 $ make codetest ... Test Summary Report --- t/codingstd/c_indent

[perl #60182] pirc/new codetest failures

fixed in r32209.

[perl #60184] [CAGE] Change the name of 'stacktrace' attribute to 'backtrace'

# New Ticket Created by Allison Randal # Please include the string: [perl #60184] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=60184 > Quick task only requiring moderate C knowledge. In the Exception PMC, change the name

Re: Why {{}} for regexp closures instead of just {}?

> On Sun, Oct 26, 2008 at 10:45 PM, Chris Dolan <[EMAIL PROTECTED]> wrote: >> S05 always uses single curlies for closures, but throughout Parrot, code >> seems to use double curlies in PGE regexps. Why is that? >> >> That is, why this: >> m/ foo {{ say "found foo" }} / >> and not this: >> m/ foo

Re: [perl #60098] [BUG] "load_bytecode" couldn't find file 'P6object.pbc'

2008/10/27 Patrick R. Michaud <[EMAIL PROTECTED]>: > On Sat, Oct 25, 2008 at 06:50:29AM -0700, François PERRAD via RT wrote: >> >> In fact, perl6.exe contains some dependencies on build tree. >> Just after a build, perl6.exe works : > > This is a known item -- see line 32 of languages/perl6/README:

Re: [perl #60168] [PATCH] Refactor Junction.

Patrick R. Michaud via RT wrote: On Mon, Oct 27, 2008 at 03:47:50AM -0700, Vasily Chekalkin wrote: I've (slightly) refactor Junction.pir. 1. Get rid of "junction_comparision_helper". Use "infix_junction_helper" instead. 2. In "infix" and "unary" junction helpers store original value in Result

[perl #60176] Rakudo fails on defining classes with core roles

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #60176] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=60176 > Rakudo r32151 can't create classes with roles from the Rakudo-defined classes. $ ./perl

[perl #60134] [TODO] Add tests for file-based interface to Configure.pl

No complaints. No failures in Smolder tests. Resolving ticket.

[perl #60178] Commit r32189 breaks Parrot on Mac OS X 10.5.4

This will be difficult to diagnose unless we do see 'make' output, so please attach a file. Alternative, go to IRC #parrot and use 'nopaste' to post.

Re: [perl #60178] Commit r32189 breaks Parrot on Mac OS X 10.5.4

On Tue, Oct 28, 2008 at 8:16 AM, James Keenan via RT <[EMAIL PROTECTED]> wrote: > This will be difficult to diagnose unless we do see 'make' output, so > please attach a file. Alternative, go to IRC #parrot and use 'nopaste' > to post. > To limit the verbosity, you could run make 2x and just send

Re: Why {{}} for regexp closures instead of just {}?

On Mon, Oct 27, 2008 at 04:07:39PM -0500, [EMAIL PROTECTED] wrote: > > On Sun, Oct 26, 2008 at 10:45 PM, Chris Dolan <[EMAIL PROTECTED]> wrote: > >> S05 always uses single curlies for closures, but throughout Parrot, code > >> seems to use double curlies in PGE regexps. Why is that? > >> > >> That

Re: [perl #60186] [PATCH] make PGE support {PIR} closures instead of just {{PIR}}

On Mon, Oct 27, 2008 at 10:24:56PM -0700, Chris Dolan wrote: > The attached patch allows one to use either single or double curlies > (or triple, etc, actually). I added disambiguation for the "{*}" > token which is now a special case of "{...}". Perhaps that latter > bit was over-engineeri

Re: Invoking PGE closures as Rakudo code

On Tue, Oct 28, 2008 at 01:50:42AM -0500, Chris Dolan wrote: > > My goal is to build arbitrarily complex data structures from closures > fired in my grammar. Specifically, I'm trying to write a PDF parser -- > my grammar is parsing correctly now, but I'd rather not have to write the > closures

Re: [perl #60186] [PATCH] make PGE support {PIR} closures instead of just {{PIR}}

On Mon, Oct 27, 2008 at 10:24:56PM -0700, Chris Dolan wrote: > As of parrot rev 32120, PGE only supports the old S05 closure syntax > that had double curlies like so > /foo {{ say "matched foo" }}/ > > The current S05 says this is legal: > /foo { say "matched foo" }/ > > This was discus

Re: [perl #60168] [PATCH] Refactor Junction.

On Tue, Oct 28, 2008 at 07:10:15PM +1100, Vasily Chekalkin wrote: >> Note that all of this effectively disappears when we have >> the dispatcher handling Junctions properly -- i.e., the >> specialized operator functions defined in Junction really >> should not exist. > > Indeed. But current state o

Re: [perl #60168] [PATCH] Refactor Junction.

Patrick R. Michaud wrote: Note that all of this effectively disappears when we have the dispatcher handling Junctions properly -- i.e., the specialized operator functions defined in Junction really should not exist. Yup, and I don't plan to spend any more time on those functions inside Juncti

Re: [perl #60168] [PATCH] Refactor Junction.

Patrick R. Michaud wrote: > On Mon, Oct 27, 2008 at 03:47:50AM -0700, Vasily Chekalkin wrote: >> I've (slightly) refactor Junction.pir. >> >> 1. Get rid of "junction_comparision_helper". Use "infix_junction_helper" >> instead. >> 2. In "infix" and "unary" junction helpers store original value in

[perl #60190] [BUG] problems with the compiler-option "-O2" on a 64bit-system

# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #60190] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=60190 > Hello I want to build parrot-RPMs on a 64bit system under Fedora 9 for the parrot-

Re: [perl #60178] Commit r32189 breaks Parrot on Mac OS X 10.5.4

Will (>), James (>>): >> This will be difficult to diagnose unless we do see 'make' output, so >> please attach a file. Alternative, go to IRC #parrot and use 'nopaste' >> to post. > > To limit the verbosity, you could run make 2x and just send us the > output of the second run, as presumably the

Re: [perl #60178] Commit r32189 breaks Parrot on Mac OS X 10.5.4

On Tue, Oct 28, 2008 at 3:00 PM, Carl Mäsak <[EMAIL PROTECTED]> wrote: > Will (>), James (>>): >>> This will be difficult to diagnose unless we do see 'make' output, so >>> please attach a file. Alternative, go to IRC #parrot and use 'nopaste' >>> to post. >> >> To limit the verbosity, you could r

Re: [perl #60190] [BUG] problems with the compiler-option "-O2" on a 64bit-system

On Tuesday 28 October 2008 07:05:47 [EMAIL PROTECTED] (via RT) wrote: > But perhaps there will someone be able to find a way to solve this problem. Can you provide a backtrace from GDB? -- c

Re: [perl #60178] Commit r32189 breaks Parrot on Mac OS X 10.5.4

On Tue, Oct 28, 2008 at 3:18 PM, Carl Mäsak <[EMAIL PROTECTED]> wrote: > "load_bytecode" couldn't find file 'PGE.pbc' > current instr.: 'parrot;PGE;Perl6Grammar;Compiler;__onload' pc 22 > (../../runtime/parrot/library/PGE/Perl6Grammar.pir:72) > called from Sub 'parrot;PGE;Perl6Grammar;Compiler;main

[perl #56382] [RFC] Making Test::Harness 3 available without including it in core parrot.

On So. 07. Sep. 2008, 15:31:49, [EMAIL PROTECTED] wrote: > This ticket has not been addressed since early July. Re-reading it now, > it seems to have two major discussion threads: one specific to > Test::Harness 3 and one relating more generally to the versions of CPAN > modules needed to configu

Re: [perl #60166] [BUG] Exception handling in parrot doesn't unwind stack.

> I'm working on a patch that defines the helper function > Parrot_ex_throw_from_op_args to simplfy the throwing in cases like this. After discussion in #parrotsketch, added this function in r3 -- Salu2

Re: [perl #60044] [BUG?] rethrow just throwing?

On Fri, 24 Oct 2008, Allison Randal wrote: > Will Coleda wrote: > > Allison Randal wrote: > > > ...you expect 'rethrow' to keep the stack trace of the original 'die'? > > Yes. > > The way to do this is to add stack trace information to the Exception's > 'stacktrace' attribute when the exception is

Re: Invoking PGE closures as Rakudo code

On Oct 28, 2008, at 10:06 AM, Patrick R. Michaud wrote: On Tue, Oct 28, 2008 at 01:50:42AM -0500, Chris Dolan wrote: My goal is to build arbitrarily complex data structures from closures fired in my grammar. Specifically, I'm trying to write a PDF parser -- my grammar is parsing correctly n

[perl #59924] [BUG] t/examples/library.t: new failure

On Sat Oct 18 09:39:52 2008, [EMAIL PROTECTED] wrote: > On Thu Oct 16 04:39:06 2008, [EMAIL PROTECTED] wrote: > [snip] > > Here is more data concerning the above test failure. > > Between r31872 (Oct 10) and r31967 (Oct 14), I used 'apt-get' to install > 4 additional Debian packages on the Linux

[perl #60178] Commit r32189 breaks Parrot on Mac OS X 10.5.4

On Tue Oct 28 12:08:05 2008, masak wrote: > Good suggestions. Here we go: . > As a (probably misleading) point of reference, here's what I got on Mac OS X 10.4 PPC in the same vicinity (95% of the way thru 'make') in a recent build: make -C compilers/pge /usr/local

[perl #59636] [BUG] t/op/bitwise.t fails on Darwin

On Wed Oct 22 19:03:27 2008, [EMAIL PROTECTED] wrote: > After yesterday's release, this passed for me on Darwin PPC 10.4 at > r32119. I'll keep my fingers crossed and keep watching the Smolder reports. > This has continued to pass for me on 10.4/PPC. Coke, if it's passing for you as well (which

[perl #60178] Commit r32189 breaks Parrot on Mac OS X 10.5.4

On Tue Oct 28 12:08:05 2008, masak wrote: > Good suggestions. Here we go: . > As a (probably misleading) point of reference, here's what I got on Mac OS X 10.4 PPC in the same vicinity (95% of the way thru 'make') in a recent build: make -C compilers/pge /usr/local

[perl #60068] [BUG] t/pmc/packfile.t: set_integer_keyed_str test failing on Darwin PPC

Still failing as of r32225; cf http://smolder.plusthree.com/app/public_projects/tap_stream/7437/260 not ok 6 - set_integer_keyed_str # Failed test 'set_integer_keyed_str' # at t/pmc/packfile.t line 140. # Exited with error code: [SIGNAL 11] # Received: # # Expected: # not equal #

Re: [perl #60166] [BUG] Exception handling in parrot doesn't unwind stack.

On Sun, Oct 26, 2008 at 10:05:21PM -0700, Vasily Chekalkin wrote: > Exception handling in parrot doesn't unwind used stack frames. > > Simple example: > > .sub 'main' > .local pmc i > i = new 'Integer' >do_loop: > say i > push_eh do_inc > $P0 = find_method i, "succ" >

Re: [perl #60166] [BUG] Exception handling in parrot doesn't unwind stack.

On Tue, Oct 28, 2008 at 10:15:32PM -0500, Patrick R. Michaud wrote: > ... As discussed in #parrotsketch > earlier today and summarized at [1], the correct form of the > above loop would have the "pop_eh" line after the do_inc label, > so that every exception handler created in the loop is removed >

Re: Invoking PGE closures as Rakudo code

On Oct 28, 2008, at 10:06 AM, Patrick R. Michaud wrote: On Tue, Oct 28, 2008 at 01:50:42AM -0500, Chris Dolan wrote: My goal is to build arbitrarily complex data structures from closures fired in my grammar. Specifically, I'm trying to write a PDF parser -- my grammar is parsing correctly n