pugs-comm...@feather.perl6.nl writes:
> +The C type is derived from C, with the additional constraint
> +that it may only contain validly encoded UTF-8. Likewise, C is
> +derived from C, and C from C.
What does "validly encoded UTF-8" mean in this context? The following
questions come to mind:
I think this proposal goes to far in the dwimmery direction-
On Sat, Jun 13, 2009 at 12:58 PM, John M. Dlugosz<2nb81l...@sneakemail.com>
wrote:
> Daniel Ruoso daniel-at-ruoso.com |Perl 6| wrote:
>>
>> So, how do I deal with a multidim array? Well, TIMTOWTDI...
>>
>> my @a = 1,[2,[3,4]];
>> say @
Apologies for the long post with mistakes in it. I'm going to try
again, biting off less.
my @g[2;2];
@g[0;0]='r0c0';
@g[0;1]='r0c1';
@g[1;0]='r1c0';
@g[1;1]='r1c1';
@g[1] is due to S09:
Multi-dimensional arrays, on the other hand, know how to handle a
multidimensional slice, with one subslice
On behalf of the Rakudo development team, I'm pleased to announce
the June 2009 development release of Rakudo Perl #18 "Pittsburgh".
Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine [1].
The tarball for the June 2009 release is available from
http://github.com/rakudo/rakudo/down
> Matthew Walton wrote:
> > If a user of your API contrives to make it change while you're
> > running, that's their own foot they've just shot, because they can
> > look at the signature and know the semantics of the parameter
> > passing being used and know that if they change the value external
On Fri, 19 Jun 2009, Martin D Kealey wrote:
> To that end I would propose that:
> - parameters should be read-only AND invariant by default, and
> - that invariance should be enforced passing a deep immutable clone
>(*5) in place of any object that isn't already immutable.
Sorry, typo: that
