Timothy, you raise a good point that I had been thinking about earlier as a
consequence of my proposal about comments being preserved and attached as
meta-data to what is most appropriate contextually.
I'm thinking that it should be formally defined somewhere (maybe as an extra
section in the
I had an interesting idea I wanted to put out there. If I'm being a
good boy and commenting my code, I do things like the following pseudocode:
# Get the stuff and do other stuff with it
@lines = slurp("file");
@otherlines = map { s/foo/bar/ } @lines
putfile("fi
> "KH" == Kyle Hasselbacher writes:
KH> use v6;
KH> my $s; # ! $x.defined
KH> my @a; # @a.defined
KH> That's the current Rakudo behavior. RT #64968 suggests that this is a
KH> bug. In Perl 5, @a would not be defined until something was put into
KH> it. Which should it be?
use v6;
my $s; # ! $x.defined
my @a; # @a.defined
That's the current Rakudo behavior. RT #64968 suggests that this is a
bug. In Perl 5, @a would not be defined until something was put into
it. Which should it be? I'd like to write a test for this.
Thanks.
Kyle.
Moritz Lenz wrote:
t/spec/S02-builtin_data_types/unicode.t has tests like this:
# LATIN CAPITAL LETTER A, COMBINING GRAVE ACCENT
my Str $u = "\x[0041,0300]";
is $u.bytes, 3, 'combining À is three bytes as utf8';
is $u.codes, 2, 'combining À is two codes';
is $u.graphs, 1, 'combining À is one g
