[perl #42339] [CAGE] Test Valid and Invalid Parrot Flags
I notice that the *actual* exit code I'm getting is 256. Has that changed since the OP or is there some bit-shifting going on here? I also notice that the same exit code is generated regardless of whether the option is valid or not. Is that the behavior we desire?
Re: [perl #55666] [PATCH] Fix xor behavior according to r14547 in [perl6-synopsis]
Patrick R. Michaud wrote: I'll either adjust the C node to have a 'false value returns' attribute, or move it entirely into the Perl 6 compiler. +1 for 'move entirely'. It's very Perl6 specific behavior. -- Bacek
Re: [perl #42339] [CAGE] Test Valid and Invalid Parrot Flags
> I notice that the *actual* exit code I'm getting is 256. Has that > changed since the OP or is there some bit-shifting going on here? > If you are testing the return from a system call, "To get the actual exit value, divide by 256. (The lower eight bits are set if the process died from a signal.)" Thus spake "Perl in a Nutshell", 2nd Ed. p139. -- Email and shopping with the feelgood factor! 55% of income to good causes. http://www.ippimail.com
Release warm-up! Call for NEWS, CREDITS and PLATFORMS updates.
Greetings, Parrot next release is on schedule for next Tuesday, June 17th. Unless any showstopping bugs are reported in the next few days. In preparation, please update NEWS with the latest hackings, also report any PLATFORMS updates. Try to run 'make fulltest' on every architecture that you can get your hands on. Please put major updates or refactors on hold until release. Testing, documention updates and bug fixes are most welcome. Thanks everyone for the commitment to the project. Best Regards, Nuno 'smash' Carvalho
Re: [perl #42339] [CAGE] Test Valid and Invalid Parrot Flags
On Fri, Jun 13, 2008 at 8:19 AM, James Keenan via RT <[EMAIL PROTECTED]> wrote: > I notice that the *actual* exit code I'm getting is 256. Has that > changed since the OP or is there some bit-shifting going on here? > > I also notice that the same exit code is generated regardless of whether > the option is valid or not. Is that the behavior we desire? > Taking ajr's email into account, here's what I'm seeing for exit codes at the shell: $ ./parrot -BLORG Option -B not known parrot -[abcCEfgGhjprStvVwy.] [-d [FLAGS]] [-D [FLAGS]][-O [level]] [-o FILE] $ echo $? 1 $ ./parrot parrot -[abcCEfgGhjprStvVwy.] [-d [FLAGS]] [-D [FLAGS]][-O [level]] [-o FILE] $ echo $? 0 -- Will "Coke" Coleda
Re: Release warm-up! Call for NEWS, CREDITS and PLATFORMS updates.
On Friday 13 June 2008 10:35:29 Nuno 'smash' Carvalho wrote: > Please put major updates or refactors on hold until release. Testing, > documention updates and bug fixes are most welcome. Would you like all hackathon progress to go in a branch then? I think we could get a lot of interesting things done in trunk by Sunday night, leaving a couple of days of testing before the release. Would that be a comfortable enough buffer? -- c
Re: Release warm-up! Call for NEWS, CREDITS and PLATFORMS updates.
On Fri, Jun 13, 2008 at 7:27 PM, chromatic <[EMAIL PROTECTED]> wrote: > On Friday 13 June 2008 10:35:29 Nuno 'smash' Carvalho wrote: > >> Please put major updates or refactors on hold until release. Testing, >> documention updates and bug fixes are most welcome. > > Would you like all hackathon progress to go in a branch then? I think we > could get a lot of interesting things done in trunk by Sunday night, leaving > a couple of days of testing before the release. Would that be a comfortable > enough buffer? I think work can go intro trunk, still plenty of time for testing before the release. As long as people help testing on Monday across all architectures every has access to. > -- c ./smash
Re: Pb with src/packdump.c
On Friday 13 June 2008 05:01:44 François Perrad wrote: > since r28250, 'make world' fails with a linking problem on Ubuntu & Windows > > undefined reference to 'CONST_STRING' Thanks, fixed in r28327. -- c
Re: [perl #55594] Modify parser to allow empty semicolon ';' terminated statement
So, since Rakudo's current grammar pretty much matches what STD.pm
has here, I'd prefer that we figure out how STD.pm is handling
empty statements and do that.
Thanks again!
Pm
As far as I can tell, STD.pm handles this problem in "token statement",
as shown below. If you modify the statement rule in grammar.pg the same
way and make a small change to actions.pm, parrot/perl6 seems to handle
empty ; statements fine and passes the small, included, test suite. The
revised patches are attached.
token statement {
...
| {*} #= null
...
}
Index: src/parser/grammar.pg
===
--- src/parser/grammar.pg (revision 28329)
+++ src/parser/grammar.pg (working copy)
@@ -203,6 +203,7 @@
{*} #= statement_mod_cond
|| {*} #= expr
]
+| {*} #= null
}
rule statement_control {
Index: src/parser/actions.pm
===
--- src/parser/actions.pm (revision 28329)
+++ src/parser/actions.pm (working copy)
@@ -111,6 +111,9 @@
if $key eq 'statement_control' {
$past := $( $ );
}
+elsif $key eq 'null' {
+$past := PAST::Stmts.new(); # empty stmts seem eliminated by TGE
+}
else {
my $expr := $( $ );
if $expr.WHAT() eq 'Block' && !$expr.blocktype() {
Index: t/spectest_regression.data
===
--- t/spectest_regression.data (revision 28329)
+++ t/spectest_regression.data (working copy)
@@ -15,6 +15,7 @@
S03-operators/not.t # pure
S03-operators/relational.t # pure
S03-operators/true.t# pure
+S04-statements/terminator.t # pure
S04-statements/try.t
S04-statements/until.t # pure
S04-statements/while.t
use v6;
use Test;
plan 9;
# L
# the 'empty statement' case responsible for the creation of this test file
eval_lives_ok(';', 'empty statement');
eval_lives_ok('my $x = 2', 'simple statement no semi');
eval_lives_ok('my $x =
9', 'simple statement on two lines no semi');
eval_lives_ok('my $x = 2;', 'simple statement with semi');
eval_lives_ok('{my $x = 2}', 'end of closure terminator');
eval_lives_ok('{my $x =
2;}', 'double terminator');
eval_lives_ok(';my $x = 2;{my $x = 2;;};', 'extra terminators');
eval_dies_ok('{my $x = 2;', 'open closure');
eval_dies_ok('my $x = ', 'incomplete expression');
[perl #54740] [PATCH] Fixing operator form for 'grep' and 'first'
Fixed in r28078, thanks! Pm
[perl #55338] sub form of WHAT() missing
Fixed in r28162, thanks! Pm
[perl #55756] [BUG] nmake realclean fails on windows
# New Ticket Created by Will Coleda # Please include the string: [perl #55756] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=55756 > I can't do an nmake realclean on windows at the moment, because the O_FILES list is too long. A quick fix would probably be to quote the elements and let perl expand them, rather than letting the shell do it for us. -- Will "Coke" Coleda
[svn:parrot-pdd] r28331 - in trunk/docs: . pdds/draft
Author: coke Date: Fri Jun 13 21:41:56 2008 New Revision: 28331 Modified: trunk/docs/pdds/draft/pdd19_pir.pod Changes in other areas also in this revision: Modified: trunk/docs/compiler_faq.pod trunk/docs/vtables.pod Log: [DOCS] remove reference to chip-as-architect; assume our developers know how POD works. Modified: trunk/docs/pdds/draft/pdd19_pir.pod == --- trunk/docs/pdds/draft/pdd19_pir.pod (original) +++ trunk/docs/pdds/draft/pdd19_pir.pod Fri Jun 13 21:41:56 2008 @@ -13,10 +13,6 @@ This document describes PIR, a stable, middle-level language for both compiler and human to target on. -=head1 VERSION - -$Revision$ - =head1 DESCRIPTION PIR is a stable, middle-level language intended both as a target for the
Re: [svn:parrot-pdd] r28331 - in trunk/docs: . pdds/draft
On Sat, Jun 14, 2008 at 12:41 AM, <[EMAIL PROTECTED]> wrote: > Author: coke > Date: Fri Jun 13 21:41:56 2008 > New Revision: 28331 > > Modified: > trunk/docs/pdds/draft/pdd19_pir.pod > > Changes in other areas also in this revision: > Modified: > trunk/docs/compiler_faq.pod > trunk/docs/vtables.pod > > Log: > [DOCS] remove reference to chip-as-architect; assume our developers know how > POD works. ... Whoops and accidentally commit 2 other files in addition to the one I had intended to. Some updates to the PDD here to remove the useless VERSION and updates to the compiler faq to modernize it slightly. -- Will "Coke" Coleda
