Onward & Upward: More New Assignments

2006-07-28 Thread Allison Randal
Another conference, and another opportunity to meet and talk face-to-face. I'm pleased to announce that Patrick will be taking on the primary development and maintenance of TGE. He and I will continue working together on the architecture of TGE and rest of the compiler tool suite. Patrick need

Re: [perl #39988] [BUG] Exceptions + Vtable Methods

2006-07-28 Thread Bob Rogers
From: Leopold Toetsch <[EMAIL PROTECTED]> Date: Thu, 27 Jul 2006 20:50:18 +0200 Am Donnerstag, 27. Juli 2006 19:44 schrieb Matt Diephouse: > Running this gives: > >    caught >    No exception to pop. PIR code running on behalf of a vtable (or MMD) function is implemented

Re: [perl #39986] Create Default PackFile for New Interpreter (Parrot C API)

2006-07-28 Thread chromatic
On Friday 28 July 2006 10:23, Leopold Toetsch via RT wrote: > Am Freitag, 28. Juli 2006 18:41 schrieb chromatic: > > Hm, sort of.  Is there any reason not to call it from Parrot_new() and > > not make the C API users do it? > > Well, when the next (and maybe common) step is: > > pf = Parrot_rea

Re: [perl #39997] [PATCH] PGE P5 Test Cleanup

2006-07-28 Thread jerry gay
On 7/28/06, jerry gay <[EMAIL PROTECTED]> wrote: thanks for the effort! however, i don't want to apply this patch as it is. 're_tests' was stolen directly from perl5's test suite. the idea is that the test data this file contains is implementation-independent. therefore, if some other crazy perso

Re: [perl #39997] [PATCH] PGE P5 Test Cleanup

2006-07-28 Thread jerry gay
On 7/28/06, via RT David Romano <[EMAIL PROTECTED]> wrote: # New Ticket Created by "David Romano" # Please include the string: [perl #39997] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39997 > I've updated the documentat

Re: [perl #39986] Create Default PackFile for New Interpreter (Parrot C API)

2006-07-28 Thread Leopold Toetsch
Am Freitag, 28. Juli 2006 18:41 schrieb chromatic: > Hm, sort of.  Is there any reason not to call it from Parrot_new() and not > make the C API users do it? Well, when the next (and maybe common) step is: pf = Parrot_readbc(interp, sourcefile); then the creation of the dummy PF structure was

Re: [svn:perl6-synopsis] r9725 - doc/trunk/design/syn

2006-07-28 Thread Audrey Tang
在 2006/7/28 上午 7:54 時,Aaron Crane 寫到: The motivation for s/environmental/contextual/ is clear: avoiding a term that's already used for something else. But, on the same grounds, I'm not sure that "contextual" is the right term, and especially not Ccontext> -- Perl already has contexts, and

[perl #39995] [PATCH] Minor patch for config/gen/makefiles/editor.in failing copying files

2006-07-28 Thread via RT
# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #39995] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39995 > Hi parrot-team, in my cygwin environment (at work) 'make vim-install' fails with o

Re: [perl #39986] Create Default PackFile for New Interpreter (Parrot C API)

2006-07-28 Thread chromatic
On Friday 28 July 2006 07:26, Guest via RT wrote: > This should be fixed now with r13613. Hm, sort of. Is there any reason not to call it from Parrot_new() and not make the C API users do it? I don't really want to require them to understand the use of packfiles or pull in parrot/packfile.h e

[perl #40002] TGE Refactor / Compiler Tools Object

2006-07-28 Thread via RT
# New Ticket Created by Kevin Tew # Please include the string: [perl #40002] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40002 > What bullet items will the TGE refactor consist of? * better command-line arg processor, l

Re: [svn:perl6-synopsis] r9725 - doc/trunk/design/syn

2006-07-28 Thread Aaron Crane
[EMAIL PROTECTED] writes: > Log: > Change "env" variables to "context" variables. > -$+foo environmental variable > +$+foo contextual variable > -ENV > +CONTEXT > SUPER > COMPILING > -lexical variable must be declared using "C" rather than C to be > +lexical

PGE/TGE and the future.

2006-07-28 Thread Kevin Tew
I'm seeking information regarding TGE's design goals, aspirations, future plans, etc. I see that Perl6 implements its own version of PAST and POST nodes. Is it possible to share basic PAST and POST nodes and extend them for particular HLL needs? I know that different HLLs share a lot of the