Re: S26 - The Next Generation

2009-09-21 Thread Damian Conway
Jon Lang asked: > Not actually S26; but closely related: should $=POD and .WHY be > read-only? I had assumed so. > Also, should there be other Pod variables besides $=POD? > If so, which ones? The original idea was that every Pod block with any kind of TYPENAME would be available as $=TYPENAME

r28351 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: lwall Date: 2009-09-22 03:53:43 +0200 (Tue, 22 Sep 2009) New Revision: 28351 Modified: docs/Perl6/Spec/S03-operators.pod Log: [S03] more clarifications of autogenerated generator functions, pmichaud++ Modified: docs/Perl6/Spec/S03-operators.pod

r28348 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: lwall Date: 2009-09-22 00:09:17 +0200 (Tue, 22 Sep 2009) New Revision: 28348 Modified: docs/Perl6/Spec/S03-operators.pod Log: [S03] revise thinko spotted by spinclad++ Modified: docs/Perl6/Spec/S03-operators.pod === --- d

r28347 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: lwall Date: 2009-09-21 23:26:58 +0200 (Mon, 21 Sep 2009) New Revision: 28347 Modified: docs/Perl6/Spec/S03-operators.pod Log: typos Modified: docs/Perl6/Spec/S03-operators.pod === --- docs/Perl6/Spec/S03-operators.pod 2

r28346 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: lwall Date: 2009-09-21 23:12:29 +0200 (Mon, 21 Sep 2009) New Revision: 28346 Modified: docs/Perl6/Spec/S03-operators.pod Log: [S03] missing commas Modified: docs/Perl6/Spec/S03-operators.pod === --- docs/Perl6/Spec/S03-op

r28345 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: moritz Date: 2009-09-21 23:01:49 +0200 (Mon, 21 Sep 2009) New Revision: 28345 Modified: docs/Perl6/Spec/S08-capture.pod Log: [S08] use POD markup where appropriate Also use non-breaking space for "Perl?\194?\1605" and "Perl?\194?\1606" Modified: docs/Perl6/Spec/S08-capture.pod ===

r28344 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: lwall Date: 2009-09-21 22:57:15 +0200 (Mon, 21 Sep 2009) New Revision: 28344 Modified: docs/Perl6/Spec/S03-operators.pod docs/Perl6/Spec/S09-data.pod Log: [S03,S09] Range objects are now primarily intervals in C Extend dwimminess of series to handle steps and limits readably

r28342 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: ruoso Date: 2009-09-21 22:01:50 +0200 (Mon, 21 Sep 2009) New Revision: 28342 Modified: docs/Perl6/Spec/S08-capture.pod Log: [S08] enforce correct precedence, as pointed out by pmichaud++ Modified: docs/Perl6/Spec/S08-capture.pod =

r28341 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: ruoso Date: 2009-09-21 21:58:46 +0200 (Mon, 21 Sep 2009) New Revision: 28341 Modified: docs/Perl6/Spec/S08-capture.pod Log: [S08] enforce correct precedence, as pointed out by pmichaud++ Modified: docs/Perl6/Spec/S08-capture.pod =

r28340 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: ruoso Date: 2009-09-21 21:21:37 +0200 (Mon, 21 Sep 2009) New Revision: 28340 Modified: docs/Perl6/Spec/S08-capture.pod Log: [S08] another typo by mberends++, s/list/array/ as pointed by PerlJam++ and pmichaud++ Modified: docs/Perl6/Spec/S08-capture.pod

Re: r28339 - docs/Perl6/Spec

2009-09-21 Thread Jon Lang
On Mon, Sep 21, 2009 at 12:01 PM, wrote: > @@ -65,9 +65,9 @@ > >  The basic underlying concept is that a Parcel behaves much like a >  list, but it doesn't enforce any context, in a way that no flattening > -or coercion is made. When you use the Positional API on a Parcel, it > -will include all t

r28339 - docs/Perl6/Spec

2009-09-21 Thread pugs-commits
Author: ruoso Date: 2009-09-21 21:01:22 +0200 (Mon, 21 Sep 2009) New Revision: 28339 Modified: docs/Perl6/Spec/S08-capture.pod Log: [S08] small fixes by mberends++ Modified: docs/Perl6/Spec/S08-capture.pod === --- docs/Perl6/Spec/

Re: [perl #69194] rakudo 2009-08 and when with lists

2009-09-21 Thread David Green
On 2009-Sep-20, at 12:48 am, Larry Wall wrote: Yes, I think it's fair to say that either list context OR a :by turns a Range into a RangeIterator that matches like a list. Hence, this ought to match: (1,3,5) ~~ (1..5 :2by) OK; but I still have to ask why it returns a RangeIterator instead