i'm afraid you didn't read the docs very closely...
Returns the contents of a directory as a lazy list of IO::Path objects
stringifying an IO::Path object gives you a large string.
the examples in the docs take up more room than the description of the
routine. here's the first:
Examples:
> #
you want a negative lookahead assertion, which are described (with an
example) at https://docs.perl6.org/language/regexes#Lookahead_Assertions
On Thu, May 3, 2018 at 3:10 AM, Todd Chester wrote:
> Hi All,
>
> What I am trying to do is to replace a quote `"`
> with
On Wed, Oct 24, 2012 at 5:35 AM, Marc Chantreux kha...@phear.org wrote:
Cannot assign to a non-container
in sub infix:= at src/gen/CORE.setting:11692
in block at /tmp/ZZZ:4
you're attempting to modify a string constant, which cannot be
modified. try something like (untested):
On behalf of the Rakudo development team, I'm pleased to announce
the September 2009 development release of Rakudo Perl #21 Seattle.
Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine [1].
The tarball for the September 2009 release is available from
On Sun, Oct 26, 2008 at 10:45 PM, Chris Dolan [EMAIL PROTECTED] wrote:
S05 always uses single curlies for closures, but throughout Parrot, code
seems to use double curlies in PGE regexps. Why is that?
That is, why this:
m/ foo {{ say found foo }} /
and not this:
m/ foo { say found foo }
On Mon, Oct 6, 2008 at 5:49 AM, Elyse M. Grasso
[EMAIL PROTECTED] wrote:
My company sells an application that links a bugtracking tool with an SCM tool
so that, for example, the files changed for each bug are recorded in the
bugtracking tool. It is currently written in (mostly)
On 9/20/06, Fagyal Csongor [EMAIL PROTECTED] wrote:
I was wondering if there is (or there should be) a documentation on how
to elegantly write Perl6 code.
yes, there should be.
I am afraid that when I will be starting to write Perl6 code, it will be
too much Perl5-ish, and I will end up