Building a Fedora package

2006-07-08 Thread Steven Pritchard
I've been working on building Fedora Extras packages for parrot and pugs off and on for the last couple of weeks. I have something that works fine on i386, but on x86_64 there are two issues. First, there is a hardcoded "lib" somewhere that I can't seem to find. On x86_64, libraries should get dr

PDD 23 Exceptions - ready for implementation

2006-07-08 Thread Allison Randal
Chip did a fantastic job on the Exceptions PDD. With a few refinements, I'm pronouncing it "ready to implement". We'll certainly work out more details as we go along, but the best way to test the design is to start on the code. Allison

[svn:parrot-pdd] r13214 - in trunk: . docs/pdds

2006-07-08 Thread allison
Author: allison Date: Sat Jul 8 16:48:27 2006 New Revision: 13214 Modified: trunk/docs/pdds/pdd23_exceptions.pod Changes in other areas also in this revision: Modified: trunk/ (props changed) Log: [EMAIL PROTECTED]: allison | 2006-07-08 16:37:32 -0700 [pdd23]: Answered some questions

Parrot Exceptions

2006-07-08 Thread Vishal Soni
Hi, I would like to throw a Parrot Exception from IMCC to the calling program instead of terminating IMCC when a parse error occurs. Are there some example in Parrot as to how to throw a Parrot exception and how to catch it? -Vishal

Re: A PDD for dynamic-wind?

2006-07-08 Thread Chip Salzenberg
On Sat, Jul 08, 2006 at 05:10:57PM -0400, Bob Rogers wrote: >And my intended implementation of dynamic-wind actually does require >its own stack, separate from the current control stack . .. > > Is there a PDD forthcoming? If not (or even if so), would you (Allison > now, presumably?) lik

Re: Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-08 Thread Matt Diephouse
Chip Salzenberg <[EMAIL PROTECTED]> wrote: { Language implementors, please know I'm going to do everything I can to make every commit break nothing. I did pretty well when I made namespace [''] stop being [] -- I fixed all the HLLs in the selfsame patch, except two bits of code generation

[perl #39768] [TODO] Tcl - Switch to runtime errors?

2006-07-08 Thread via RT
# New Ticket Created by Matt Diephouse # Please include the string: [perl #39768] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39768 > The official Tcl implementation doesn't throw any errors at compile time because it

A PDD for dynamic-wind?

2006-07-08 Thread Bob Rogers
From: Chip Salzenberg <[EMAIL PROTECTED]> Date: Sat, 24 Jun 2006 21:56:32 -0700 On Sat, Jun 24, 2006 at 11:18:41PM -0400, Bob Rogers wrote: > Such an implementation is truly and utterly stackless, which means that > dynamic-wind needs to keep its own stack explicitly, and similarly

Re: pdd21 vs. find_global

2006-07-08 Thread Chip Salzenberg
On Sat, Jul 01, 2006 at 10:37:59PM -0500, Allison Randal wrote: > I'm more inclined to say find_global just shouldn't accept a namespace PMC > as an argument. For those who aren't reading the subversion logs: 1. Why aren't you? :-) 2. I've done this -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-08 Thread Chip Salzenberg
{ Language implementors, please know I'm going to do everything I can to make every commit break nothing. I did pretty well when I made namespace [''] stop being [] -- I fixed all the HLLs in the selfsame patch, except two bits of code generation in TGE and PGE, which I fixed when they were

bsr/ret, continuations, and other stack rewinding bugs

2006-07-08 Thread Bob Rogers
From: Allison Randal <[EMAIL PROTECTED]> Date: Wed, 05 Jul 2006 00:02:53 -0700 Bob Rogers wrote: >If, as seems likely, exception bookkeeping is moved to a separate > stack in the interpreter (with or without dynamic-wind actions), then > C/C addresses can stay in the Parrot_C

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-08 Thread Chip Salzenberg
On Thu, Jul 06, 2006 at 05:39:45PM -0700, jerry gay wrote: > am i silly to think that if i'm looking for globals from the current > namespace, they're just as likely to be found closer to the namespace > root, than further away? perhaps something like > >.namespace [ 'Foo'; 'Bar' ] >$P0 =