I backlogged. TimToady, you said " I expect that specs to get filled out with P5ish carryovers as the entire P5 test suite (core parts, at least) are ported over to P6, and people notice there's no place to L<> to, and do some cagecleaning on the specs."

"This example shows that comprehensions are not restricted to lists. The previous program uses iterators instead. Every datatype that supports the operations filter, map, and flatMap (with the proper types) can be used in sequence comprehensions."

audreyt, TimToady: :($ : $x) is precisely what I had been parsing :(: $x) as. I need to think about this some more to figure out a predictive parsing strategy - there's already a comment in the code about how I'm unhappy with the first param being parsed twice...

r13255 | putter++ | Prelude.pm - Added *pi(), for backwards compatibility. This is non-spec. S29 says use Math::Basic :constants is needed to get pi. That's next. I would have liked to ::= Math::Basic::pi, but that wasn't working in the Prelude.

rarely dreams of himself at all and when he does - it is almost never with people he knows - and on those rare occasions that he does dream of himself and people that he knows - it is even rarer that it is in the present (usually from highschool)

@tell TimToady can you take some cycles and dewarnock gaal's Unpacking tree thread? I think my S03 patch (r11725) answers that, but both my patch and gaal's interpretation would benefit form some sanity checks..

Hmm. Say a file M.pm contains sub *f() is export {3}. You then see f when you use M;. Is there an _inline_ equivalent of M.pm? Ie, declare a module M which isnt imported until used? module M { sub &f() is export {3} } smashes f immediately...

since I'm 0 for 2 this morning, could I get someone to reality check me on the following. Math::Basic is a module. Some of it is always available, some only on use(). Two deisign optionis. Prelude.pm could require() a normal Basic.pm. Slow. Or Prelude could contain the always available (like now), and Basic be

audreyt: pugs design guidance question. Couple of options. Motivated by it seeming undesirable that a Math::Basic.pm get use()d, and loaded, by Prelude, all the time. (1) use precompiled_modules, which should probably then be turned on by default.

(3) ... "putter, work on something else!". Prelude-ification of primitives having proved a minefield in the past, perhaps it is no longer a top of the todo list objective(?), and I should leave it alone until things are more stable.

reparse is currently cheap. 1) is most sensible and is _much_ easier with newExp (less recursive Pad bookkeeping). probably prelude should be renamed GLOBAL.pm or some such at some point. and yes I'm sleeping :)

r13271 | Limbic_Region++ | Added dependency on List::Util and support for Parallel::ForkManger to allow Win32 concurrency. Please revert at the first sign of trouble as this has not been heavily tested

i'm starting to think we might need a Makefile.PL pumpking soon. i'm having to touch my makefile old for diffs i don't care about (or exclude Makefile.PL from updating until a diff comes that i do care about)... 'svn update; make' is almost guaranteed to cause a clean