r27399 - docs/Perl6/Spec

2009-07-03 Thread pugs-commits
Author: lwall Date: 2009-07-04 05:34:15 +0200 (Sat, 04 Jul 2009) New Revision: 27399 Modified: docs/Perl6/Spec/S04-control.pod Log: [S04] allow certain value-producing blocks as statement prefixes Modified: docs/Perl6/Spec/S04-control.pod ==

r27385 - docs/Perl6/Spec

2009-07-03 Thread pugs-commits
Author: moritz Date: 2009-07-03 18:48:33 +0200 (Fri, 03 Jul 2009) New Revision: 27385 Modified: docs/Perl6/Spec/S04-control.pod Log: [S04] 'constant' now scopes like 'our' TimToday++ changed that in S03 a while back, and forgot to update it here too. Modified: docs/Perl6/Spec/S04-control.pod

Re: r27312 - docs/Perl6/Spec

2009-07-03 Thread Larry Wall
On Mon, Jun 29, 2009 at 09:14:10PM -0700, Darren Duncan wrote: > pugs-comm...@feather.perl6.nl wrote: >> +When it happens that the same module is available from more than one >> +authority, and the desired authority is not specified by the C, >> +the version lineage that was created first wins, unl

Re: XOR does not work that way.

2009-07-03 Thread Larry Wall
On Fri, Jul 03, 2009 at 09:40:12AM +0200, TSa wrote: > I see. But I wouldn't make that an exception but ^^ returns a tristate > value instead of boolean. The third state besides True and False is > TooMany that evaluates to False in boolean context. But ^^ can react > to it as you describe. That so

Re: XOR does not work that way.

2009-07-03 Thread TSa
HaloO, Martin D Kealey wrote: Assuming you meant "^^" rather than "&&", then under my proposal, that's not the case. Of course! Silly me, sorry. In particular, True ^^ True evaluates to TooManyException. If that exception is implicitly thrown, then that's what you get from the whole express