Stephen P. Potter writes: > Great idea. I'd love to see us come up with some "meta" RFCs which say > what the main goals of perl6 are. Then we could align the current RFCs > with those meta RFCs to make sure we're meeting those goals. Highly unlikely to happen, as we have lots of people with different goals for perl6. Larry might not pick one group of people and exclude the others, so it'd be premature for us to do so. I've RFCed making m mandatory on matches, which would remove some of the current tokenizing confusion. I'm open to others. Nat
- RFC 135 (v2) Require explicit m on matches, even with ... Perl6 RFC Librarian
- Re: RFC 135 (v2) Require explicit m on matches, e... Bart Lateur
- Re: RFC 135 (v2) Require explicit m on matche... Nathan Torkington
- Re: RFC 135 (v2) Require explicit m on ma... Johan Vromans
- Re: RFC 135 (v2) Require explicit m o... Stephen P. Potter
- Re: RFC 135 (v2) Require explici... Bart Lateur
- Re: RFC 135 (v2) Require exp... Carl Johan Berglund
- Re: RFC 135 (v2) Require explici... Nathan Torkington
- Re: RFC 135 (v2) Require exp... Tom Christiansen
- Re: RFC 135 (v2) Require... John Porter
- Re: RFC 135 (v2) Require... Peter Scott
- Re: RFC 135 (v2) Require... Tom Christiansen
- Re: RFC 135 (v2) Require... Nathan Torkington
- Re: RFC 135 (v2) Require... Nathan Torkington
- Re: RFC 135 (v2) Require... Bart Lateur
- Re: RFC 135 (v2) Require... Nathan Torkington
- Re: RFC 135 (v2) Require... Tom Christiansen
- Re: RFC 135 (v2) Require... Casey R. Tweten