Re: perl6-synopsis svn

2007-02-22 Thread Patrick R. Michaud
On Fri, Feb 23, 2007 at 12:35:15AM +, Blair Sutton wrote: > Hi Larry > > Sorry if this is a silly question but I haven't been able to find the > answer. Is the perl6-synopsis SVN repository publicly available or is it > in the same repository as that of Parrot or Pugs? The versions that app

perl6-synopsis svn

2007-02-22 Thread Blair Sutton
Hi Larry Sorry if this is a silly question but I haven't been able to find the answer. Is the perl6-synopsis SVN repository publicly available or is it in the same repository as that of Parrot or Pugs? Thanks in advance Blair

[perl #41583] Tail calls from within vtable methods broken

2007-02-22 Thread via RT
# New Ticket Created by Bram Geron # Please include the string: [perl #41583] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41583 > --- osname= linux osvers= 2.6.18.3 arch= i486-linux-gnu-thread-multi cc= cc --- Flag

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

2007-02-22 Thread larry
Author: larry Date: Thu Feb 22 16:32:25 2007 New Revision: 13703 Modified: doc/trunk/design/syn/S06.pod Log: Clarify that a named argument may name either the label or the variable name. Modified: doc/trunk/design/syn/S06.pod ==

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

2007-02-22 Thread larry
Author: larry Date: Thu Feb 22 14:00:38 2007 New Revision: 13702 Modified: doc/trunk/design/syn/S02.pod Log: typo from aaroncrane++ Modified: doc/trunk/design/syn/S02.pod == --- doc/trunk/design/syn/S02.pod(o

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

2007-02-22 Thread larry
Author: larry Date: Thu Feb 22 13:06:22 2007 New Revision: 13701 Modified: doc/trunk/design/syn/S02.pod Log: Change hardwired 8 to $?TABSTOP // 8 for heredocs Modified: doc/trunk/design/syn/S02.pod == --- doc/trunk/d

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

2007-02-22 Thread Aaron Crane
[EMAIL PROTECTED] writes: > +be referred to as C<< COMPILING<$?LINE> >> if the bare C<$?LINE> would That looks like it's missing a double-colon. -- Aaron Crane

Re: Relief for rw/ro

2007-02-22 Thread Dr.Ruud
Steve Lukas schreef: > In between, I think 'variable' is too long, so: > $code =~ s/variable/vari/g; I don't think it is too long, since most of the times you don't need to mention it. Could 'rw' be an alias? my rw @heredoc_stubs is context = (); my @heredoc_stubs is rw context = (); my

[perl #41584] [TODO] Update RELEASE_INSTRUCTIONS with details for updating the website

2007-02-22 Thread via RT
# New Ticket Created by Patrick R. Michaud # Please include the string: [perl #41584] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41584 > The RELEASE_INSTRUCTIONS file needs an "update website" step added to it. Summary

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

2007-02-22 Thread larry
Author: larry Date: Thu Feb 22 12:51:15 2007 New Revision: 13700 Modified: doc/trunk/design/syn/S02.pod doc/trunk/design/syn/S03.pod doc/trunk/design/syn/S06.pod Log: More Y XX -> Z X clarifications Now allow "constant $?TABSTOP = 4" syntax for user to set compiler variables. Modified:

Parrot 0.4.9 released!

2007-02-22 Thread Patrick R. Michaud
On behalf of the Parrot team, I'm proud to announce Parrot 0.4.9, "Socorro." Parrot (http://parrotcode.org) is a virtual machine aimed at running all dynamic languages. Parrot 0.4.9 can be obtained via CPAN (soon), or follow the download instructions at http://www.parrotcode.org/source.html . For

Re: [perl #41579] [BUG] t/pmc/ref.t, t/pmc/threads.t file with -C runcore

2007-02-22 Thread chromatic
On Thursday 22 February 2007 08:41, Patrick R.Michaud wrote: > While running 'make fulltest' for the 0.4.9 release, I'm getting > two failing tests under the -C (CGP) runcore (r17148): > > Failed Test Stat Wstat Total Fail List of Failed > -

[perl #41582] Parrot - 0.4.11 release

2007-02-22 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #41582] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41582 > Milestone ticket for the 0.4.11 release.

[perl #41581] Parrot - 0.4.10 release

2007-02-22 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #41581] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41581 > Milestone ticket for the 0.4.10 release.

[perl #41579] [BUG] t/pmc/ref.t, t/pmc/threads.t file with -C runcore

2007-02-22 Thread via RT
# New Ticket Created by Patrick R. Michaud # Please include the string: [perl #41579] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41579 > While running 'make fulltest' for the 0.4.9 release, I'm getting two failing test

[perl #41577] docs/ROADMAP.pod refers to python bytecode translator, pie-thon test suite

2007-02-22 Thread via RT
# New Ticket Created by Patrick R. Michaud # Please include the string: [perl #41577] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41577 > In the "HIGH LEVEL LANGUAGES" section of docs/ROADMAP.pod, there are entries for "

[perl #41031] bad links in docs/ROADMAP.pod

2007-02-22 Thread Patrick R. Michaud via RT
I've gone ahead and removed the bad links from docs/ROADMAP.pod . The ROADMAP now simply says that we need to document Parrot goals and priorities. (I suggest that it go into a pdd document somewhere, if it hasn't already.) I found copies of the Chip_APW.sxi and Chip_APW.pdf files that were orig

[perl #38983] [PDD] review PDD01_overview.pod

2007-02-22 Thread Patrick R. Michaud via RT
As part of the 0.4.9 release, I've changed a section in docs/ROADMAP.pod to refer to pdd01 instead of the nonexistent "PLATFORMS" reference, since pdd01 identifies the minimum platforms needed for release. However, pdd01 is still in 'draft' status, so I'm just bumping this ticket a bit to see if w

[perl #41576] [BUG] t/pmc/pmethod_test.t fails on x86_64

2007-02-22 Thread via RT
# New Ticket Created by Patrick R. Michaud # Please include the string: [perl #41576] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41576 > I get a failure in t/pmc/pmethod_test.t when running on my system (x86_64). This

Re: Relief for rw/ro

2007-02-22 Thread Steve Lukas
PS: In between, I think 'variable' is too long, so: $code =~ s/variable/vari/g; IMHO C is better than C because C doesn't look like a special thing, but it is. I feel that the most usual cases for read/write would be better readable with that approach. Instead of C<$res=funcy($foo is rw);> i

Fwd: Preliminary notes for 0.4.9 release

2007-02-22 Thread Nuno Carvalho
Greetings, On 2/22/07, chromatic <[EMAIL PROTECTED]> wrote: On Wednesday 21 February 2007 21:21, Patrick R. Michaud wrote: > 1. The t/library/pg.t tests require libpq.so to be installed > in order to run -- should I be testing ('make fulltest') with > this library installed? They should skip

Re: [perl #41549] [PATCH] fixes :vtable pragma for .pbc files

2007-02-22 Thread Jonathan Worthington
Alek Storm (via RT) wrote: This patch resolves the problem mentioned in Patrick's replies to #40626 and #41364 that bytecode does not store the :vtable pragma. ... I've looked over this patch and it looks pretty good to me. There's release stuff ongoing at the moment, so unless anyone else o

Re: Preliminary notes for 0.4.9 release

2007-02-22 Thread Allison Randal
Patrick R. Michaud wrote: I think I prefer to take one night's rest and get it right in the morning, than to force it out this evening and perhaps have to clean up a lot of small mistakes.) Sensible. 1. The t/library/pg.t tests require libpq.so to be installed in order to run -- should I be

Re: [svn:parrot] r17107 - trunk/src/stm

2007-02-22 Thread Allison Randal
chromatic wrote: +if (saved_log_data == NULL) +return; + saved = saved_log_data; mem_sys_free(saved->reads); mem_sys_free(saved->writes); I'm not sure this is the right fix; there's little reason to use an STMLog PMC if it doesn't get a valid transaction log. My vo