[perl #58032] [BUG] languages/perl6/t/pmc/perl6multisub-dispatch-tiebreak.t: filename is too long

2008-08-16 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #58032] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58032 > We appear to have a coding standard which limits us to 32 characters in a file's basen

NEWS update for Parrot 0.7.0

2008-08-16 Thread Bob Rogers
From: Bob Rogers <[EMAIL PROTECTED]> Date: Fri, 15 Aug 2008 12:45:56 -0400 Parrot release 0.7.0 is due out this coming Tuesday, so now is the time to start focusing on . . . updating such things as the NEWS and PLATFORMS files . . . I've fleshed out NEWS based on "svn log"; plea

[svn:parrot-pdd] r30272 - trunk/docs/pdds

2008-08-16 Thread rgrjr
Author: rgrjr Date: Sat Aug 16 18:57:04 2008 New Revision: 30272 Modified: trunk/docs/pdds/pdd24_events.pod trunk/docs/pdds/pdd25_concurrency.pod Log: [typos] Neither pdd24_events.pod nor pdd25_concurrency.pod is in draft. Modified: trunk/docs/pdds/pdd24_events.pod ===

Re: Merged pdd25cx branch

2008-08-16 Thread Bob Rogers
From: Allison Randal <[EMAIL PROTECTED]> Date: Sat, 16 Aug 2008 17:52:08 +0200 We're going to a completely stackless virtual machine. But Parrot is already stackless. The dynamic_env slot to which I assume you refer is really a tree with upward pointers. What I need from you is info

Re: Merged pdd25cx branch

2008-08-16 Thread Allison Randal
Bob Rogers wrote: From: Allison Randal <[EMAIL PROTECTED]> The biggest changes you'll notice are the new exception system, a vastly reduced usage of the remaining stack (though it's not completely removed yet), and the fact that pushaction subs no longer fire on scope exit (pus

Re: Merged pdd25cx branch

2008-08-16 Thread Allison Randal
François Perrad wrote: Ok, Lua tests pass, but the behavior has changed. (The tests were written to check the exception message, not the full back trace) The pushaction allowed to retrieve the backtrace where the exception occurred. The backtrace from the exception handler is alway the same (d

Re: interpreter persistence issues

2008-08-16 Thread Jeff Horwitz
On Sat, 16 Aug 2008, Allison Randal wrote: Jeff Horwitz wrote: i'd like to have an option in mod_parrot to clear all user-generated data (globals, namespaces, subs, etc.) from an interpreter, leaving any bytecode that has been loaded (e.g. compilers). the point here is to eliminate problems

[perl #57942] [BUG] Smolder failure [linelength, compilers/pirc]

2008-08-16 Thread James Keenan via RT
On Fri Aug 15 18:33:59 2008, [EMAIL PROTECTED] wrote: > > And I, for one, find myself going to the Smolder site much more often > than our 'official' site these days -- precisely because I can spot new > test failures more quickly there and jump in with a quick fix. As I did just now: I refre

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

2008-08-16 Thread Allison Randal
chromatic wrote: On Thursday 07 August 2008 08:26:19 Bob Rogers wrote: I once suggested a "null register allocator" that would do this globally, but this is a better idea. The only use case I can think of is debugging, particularly of the register allocator, but that's still important. In th

Re: interpreter persistence issues

2008-08-16 Thread Allison Randal
Jeff Horwitz wrote: i'd like to have an option in mod_parrot to clear all user-generated data (globals, namespaces, subs, etc.) from an interpreter, leaving any bytecode that has been loaded (e.g. compilers). the point here is to eliminate problems caused by data persistence on hosted web serv

Re: Fwd: [perl #57656] [PROPOSAL][PIR] change PIR sugar for concat into ".." (or something else)

2008-08-16 Thread Allison Randal
Klaas-Jan Stol wrote: On Wed Aug 06 05:53:07 2008, kjs wrote: My proposal would be to change the concatenate dot into "..", which looks like it, but is more explicit, and will prevent such mistakes. I agree that there should be some change. I've run into this problem myself in the past, and i

Re: [perl #57634] [RFC] Remove ".globalconst" from PIR

2008-08-16 Thread Allison Randal
Klaas-Jan Stol wrote: Therefore, my proposal is to remove the .globalconst directive; whenever you need to have a global const, use .const outside of a subroutine. whenever you need to have a local const (in a sub), use .const inside a subroutine. If we're going to remove one, let's deprecate