On Monday 14 August 2006 18:53, jerry gay wrote:
> moving todo() info out of these test files leads to fragile
> test harnesses, as adding a test to the middle of a file will change test
> numbers. if test descriptions are used, then unique descriptions for each
> test are required. et cetera.
Su
On 8/14/06, chromatic <[EMAIL PROTECTED]> wrote:
Ugh, so this means editing the canonical test repository for every
status-changing update to every implementation? Yuck. This seems like a
problem for implementation-specific harnesses and reporting tools.
this is what prompted me to start th
Author: larry
Date: Mon Aug 14 18:38:44 2006
New Revision: 10944
Modified:
doc/trunk/design/syn/S04.pod
Log:
Constrained FIRST, NEXT, and LAST to work only at top level of loop block.
Modified: doc/trunk/design/syn/S04.pod
=
On Monday 14 August 2006 17:20, jerry gay wrote:
> > I've added the plan for the neutral todo mechanism to Pugs' TASKS
> > file, getting help from many others on #perl6. The new todo marks look
> > like this:
> >
> >todo :pugs<6.28.0>, :p6p5<0.110>, :parrot<1.00>;
> >is $got, $expected; #
Author: larry
Date: Mon Aug 14 17:53:44 2006
New Revision: 10942
Modified:
doc/trunk/design/syn/S04.pod
doc/trunk/design/syn/S06.pod
Log:
FIRST renamed to START. (FIRST now does loop initialization only.)
Minor cleanup of MAIN verbiage.
Modified: doc/trunk/design/syn/S04.pod
=
[parrot-porters and p6l have been removed from this thread, as discussion of
testing tools is not directly related to those lists]
On 8/11/06, Agent Zhang <[EMAIL PROTECTED]> wrote:
On 8/12/06, jerry gay <[EMAIL PROTECTED]> wrote:
this last testing rule i mentioned becomes somewhat problematic
[dropped perl-qa and p6l from this thread, as it's repo-related, and not
directly related to those lists]
On 8/12/06, Audrey Tang <[EMAIL PROTECTED]> wrote:
在 2006/8/12 上午 3:01 時，jerry gay 寫到：
> for "managed," i have a few ideas. currently, the suite lives in the
> pugs repo. this is a fine fi
Author: larry
Date: Mon Aug 14 12:36:02 2006
New Revision: 10940
Modified:
doc/trunk/design/syn/S02.pod
Log:
Clarified that comments may not contain unspace. agentzh++ and luqui++.
Modified: doc/trunk/design/syn/S02.pod
===
On Mon, Aug 14, 2006 at 04:01:47PM +, Luke Palmer wrote:
> What do these do?
>
> for 1,2 {
> my $code = {
> my $x;
> BEGIN { $x = 42 }
> $x;
> };
> say $code();
> }
Assuming that variables are available immediately as
they are parsed and that BEGIN
On Mon, Aug 14, 2006 at 16:01:47 +, Luke Palmer wrote:
> What do these do?
Intuition based answers:
> for 1,2 {
> my $code = {
> my $x;
> BEGIN { $x = 42 }
> $x;
> };
> say $code();
> }
I think the closure would be emitted equivalently to my $x = 4
What do these do?
for 1,2 {
my $code = {
my $x;
BEGIN { $x = 42 }
$x;
};
say $code();
}
for 1,2 {
my $code = {
state $x;
BEGIN { $x = 42 } # mind you, not FIRST
$x++;
};
say $code();
say $code();
}
fo
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Aug 14 13:15:01 2006 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
12 matches
Mail list logo
