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 graph';
Which seems to
S05 mentions the magic after pattern in two locations, but I cannot
find a specification of the interaction between after and the
ratcheting {rule/token} status.
Specifically, is
token {
... ?after x
}
going to match the same pattern as
rule {
... ?after x
}
??
I ask because (I just
Aaron Sherman wrote:
On Sun, Aug 2, 2009 at 1:10 PM, Moritz Lenz mor...@faui2k3.org wrote:
Let's pick up this old mail before it gets completely warnocked ;-)
For the record, this discussion only applies to scalar implementation
types. For example for Arrays I expect things to work by
On Sat, Aug 08, 2009 at 05:45:40PM -0400, Austin Hastings wrote:
[...]
Specifically, is
token { ... ?after x }
going to match the same pattern as
rule { ... ?after x }
??
I ask because (I just did it, and) with rules encouraging the liberal
use of whitespace, and implicitly
