, Darren Duncan dar...@darrenduncan.net wrote:
David Brunton wrote:
I notice that CKeyWeight returns False and deletes the key for a key
whose value goes to zero or less than zero, issuing a warning in the
latter case. Is it the case that CFatRat always evaluates to False
in Boolean context when
I notice that CKeyWeight returns False and deletes the key for a key
whose value goes to zero or less than zero, issuing a warning in the
latter case. Is it the case that CFatRat always evaluates to False
in Boolean context when negative?
This last SOTO re-reminded me of what an inveterate fan I am of Perl 6. Wow.
My question today is about concurrency. I can imagine how things like IPC
Mailboxes (e.g. RFC 86) happen in modules. I can also imagine why Threads
(e.g. RFC 1) should be in modules- given the obvious dependence on
From an IRC conversation earlier today:
A quick scan of S05 reveals definitions for these seven special named
assertions:
before pattern
after pattern
sp
ws
null
'...'
at($pos)
Twenty-four more are listed in docs/Perl6/Overview/Rule.pod (some of which are
used in S05, but I don't
Aaron Sherman wrote:
replies snipped /
Is the goal to avoid namespace pollution? If so, shouldn't there be a
truly metaish way of getting at the internal namespace so that someone
doesn't accidentally render an object unusable by defining the wrong
method name (which you can prevent with an
Hi all,
There is currently a mismatch between S12 and Pugs. The former specifies
$obj.META, the latter has implemented $obj.meta.
Is there any reason I shouldn't change the tests from meta to META, make the
corresponding changes in Pugs.Prim, and then fix any other examples or modules
it
