view release on metacpan or  search on metacpan

t/lib/Hailo/Test/TimToady.trn  view on Meta::CPAN

:16($ack)
didn't want to use hex and oct like Perl 5, since those are backwards; you'd think hex would *produce* a hex number
jnthn++ for pesteration
"undefined" is not meant to be a restrictive adjective :)
$x can Haz[Cheezburger]
yes, I think it was a mistake to confuse enums directly with roles
distinguishing them allows us to distinguish things that do Boolean with their own .Bool method from things that get a .Bool method via mixin of a $.Bool attribute
so now most of the type behavior more or less falls out naturally
making an enum function as a subset is perhaps still a bit forced
but I think Day.ACCEPTS just does a $arg ~~ Day.mapping.values.any
or some such
yes, I thought does/but could stant to be that one level of dwimmy
as long as the arg comes in with sufficient type info
does Enumeration maybe
the duck typing answer is that .WHAT.mapping returns something :)
yeah, tried not to put anything in that I could at least think of an implementation story
and adding .mapping really simplifies a lot of other things
unless someone says 'use DUCK_TYPING;' and then we all duck
well, we need something to keep our collective back-patting arm from going out of joint :)
You too could be an IT engineer!
.oO(so much for working on LTM this weekend... :)
my eventual goal is to have *everything* written in Perl 6...but you knew that already...
mberends: yes, verilog better watch out :)
not to mention QM...
funny that we have a reality inversion in Perl 6.  quantum operations are high-level, while low-level ones like .Bool are classical...
lunch &
still is
seems to me it oughta look like a space :)
perhaps it's a font issue
yes, we outlawed $_ in the { a => 2 } form
romanhunt: curlies have gained power by *reducing* the number of uses from what Perl 5 does, actually :)
(and cuts many of the apron strings tying current rakudo to parrot)
they've been separated for several years now
diakopter: cats can't herd other cats either
everything is important, if only as a lesson  :)
in other words, we're still groping our way forward, but we're getting much faster at it.  :)
we're hoping each redesign takes half the time of the previous
eventually Zeno loses :)
name a VM
it's been thunka
and the 3rd will be 1/2 that, then 1/4, 1/8.... :)
the problem with the second will be discovering all the place we assumed how the circularity saw worked that were wrong
*places
right now we're exploring abstract vs concrete versions of the same operation, hoping that will be an obvious place to saw
so .Str conversion might be in the VM, while ~ conversion is in P6
(and crossing our fingers that we don't end up with the too-many-levels-of-indirection problem)
pugs had a CL backend at one point, iirc
or maybe it was one of the other parsers
jnthn: my guess is that eventually parrot scraps it's internal system and bases everything off the Perl 6 types :)
*its
not exactly
it'd be a VM that happens to be written in P6
but we need to get the native types going better first
basically, I see the nqp-rx phenomenon happening all over again once we have full P6.
the first would be scratching your head?
"The origins of this VM are lost (purposefully) in the mists of time."
gotta cross the Jordan first...
well, I know who gets left behind at the Jordon, and trying not to think about that... :)
ciao
std: undef $/
std: $/ = ""
necessary when replacing with a different $/
pugs: use v5; print "howdy\n"
heh
p5 == security breach to pugs :)
sjbot: p5eval: system 'rm -rf /'
STD doesn't understant 'use v5' yet
*stand
I probably wouldn't, but diakopter might :)
and maybe run in a chroot jail
and maybe use Safe, fwiw
only takes 13 seconds on my machine
to parse all those $'s
Anonymous variable requires declarator at (eval) line 1:
and a couple deep recursion warnings :)
probably tickles lazymap too hard
funny that it kills p6eval
wow, that was fast
recompiled, still takes ~14 seconds
I think I'm probably running a 32-bit kernel
Linux edo 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 i686 GNU/Linux
oh, heh, I had the debug log turned on :)
< 1sec now
because Perl isn't even getting into the NFA on that one
Perl 5 goes to great lengths to *avoid* calling into the regex matcher
and the ab$ is special cased to fail fast
it would fail not quite so fast with just ab
but still faster than the regex would figure it out, but it'd have to scan for the constant string
and ab doesn't buy you much with boyer-moore
it'd fail abcdefg a lot faster
I'll never tell :)
make the second a a*
no, that won't work either, since your end matter can match null string
that one will be pretty slow
no, but it'll probably run a bit under 300 hours
because it's not what people want
I deny it--I've never had mono...
though, of course, there's a good chance I'd test positive for EBV
I'm not particularly interested in playing with mono yet.  Maybe after I get done with Perl 6...
yes, well, one diakopter can only go so far in emulating a flooding algorithm
too, for that matter
well, you are one the cats I don't try to herd :)
so does git :)
decommuting &
seems a bit odd to index a hash by a decimal number
as in The Emperor's New Science  :)
I'd make sure the keys of the hash aren't actually like '101'
wrong keys would certainly get you uninits
likewise if it's really returning @ instead of %
though you'd think in that case it'd complain "I'm not a hash."
also, stylistically, you don't need parens on the for loop args
and the final conditional could simply return the result of the comparison, since that's already a Bool
well, you'd have to negate it
<= maybe
and the pod has a syntax error :)
std: while($ca.next()) { }
in theory
that's because P5 doesn't support that
you need a regex engine that can ask the input system for more string for that to work
you didn't have to guess; the documents say as much :P
how big is the input?