New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grapheme-level reasoning is NYI for regexes, .chars, .ord (among others) in Rakudo #953
Comments
From @wollmers$ ./perl6 -e 'say "\c[LATIN CAPITAL LETTER A WITH DOT ABOVE, COMBINING Expected result: 1 $ ./perl6 -e 'say "\c[LATIN CAPITAL LETTER A, COMBINING DOT ABOVE, Expected result: 1 see specs: ----quote---- Helmut Wollmersdorfer |
From @wollmers$ ./perl6 -e 'say "\c[LATIN CAPITAL LETTER A, COMBINING DOT ABOVE]".ord;' Both results should be the same in grapheme mode. Grapheme mode is default. Helmut Wollmersdorfer |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/spec/S29-conversions/ord_and_chr.t commit 2f95300eed064742a91048b65ae28efea460b673 [t/spec] Test for RT #65172 Inline Patchdiff --git a/t/spec/S29-conversions/ord_and_chr.t b/t/spec/S29-conversions/ord_and_chr.t
index ee3820d..38d9a5d 100644
--- a/t/spec/S29-conversions/ord_and_chr.t
+++ b/t/spec/S29-conversions/ord_and_chr.t
@@ -121,7 +121,7 @@ my @maps = (
"\o03", 3,
);
-plan 37+@maps*2;
+plan 38+@maps*2;
for @maps -> $char, $code {
my $descr = "\\{$code}{$code >= 32 ?? " == '{$char}'" !! ""}";
@@ -152,4 +152,12 @@ is chr(104, 101, 108, 108, 111), 'hello', 'chr works with a list of ints';
#?rakudo skip 'RT #62772'
ok ord("") ~~ Failure, 'ord("") returns a Failure';
+# RT #65172
+{
+ my $rt65172a = "\c[LATIN CAPITAL LETTER A, COMBINING DOT ABOVE]";
+ my $rt65172b = "\c[LATIN CAPITAL LETTER A WITH DOT ABOVE]";
+ #?rakudo todo 'RT #65172'
+ is $rt65172a.ord, $rt65172b.ord, '.ord defaults to grapheme mode';
+}
+
#vim: ft=perl6 |
The RT System itself - Status changed from 'new' to 'open' |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/spec/S02-builtin_data_types/unicode.t commit e00ba2f74e7c0923b6550f76f6d22d10950c90a1 [t/spec] Additional tests for RT #65170 Inline Patchdiff --git a/t/spec/S02-builtin_data_types/unicode.t b/t/spec/S02-builtin_data_types/unicode.t
index 2263361..a399c9d 100644
--- a/t/spec/S02-builtin_data_types/unicode.t
+++ b/t/spec/S02-builtin_data_types/unicode.t
@@ -1,7 +1,7 @@
use v6;
use Test;
-plan 15;
+plan 17;
#L<S02/"Built-In Data Types"/".bytes, .codes or .graphs">
@@ -16,6 +16,16 @@ is "foo\r\nbar".graphs, 7, 'CRLF is 1 graph';
# Speculation, .chars is unspecced, also use Bytes etc.
is $u.chars, 1, '.chars defaults to .graphs';
+# RT #65170
+{
+ my $rt65170;
+
+ $rt65170 = "\c[LATIN CAPITAL LETTER A WITH DOT ABOVE, COMBINING DOT BELOW]";
+ is $rt65170.chars, 1, '.chars defaults to .graphs (2)';
+ $rt65170 = "\c[LATIN CAPITAL LETTER A, COMBINING DOT ABOVE, COMBINING DOT BELOW]";
+ is $rt65170.chars, 1, '.chars defaults to .graphs (3)';
+}
+
#L<S02/"Built-In Data Types"/"coerce to the proper units">
$u = "\x[41,
E1, |
The RT System itself - Status changed from 'new' to 'open' |
From @cokeOn Mon Apr 27 06:20:19 2009, helmut@wollmersdorfer.at wrote:
No change as of rakudo 545638a -- |
From @cokeOn Sat Aug 15 21:08:05 2009, KyleHa wrote:
Fudged this test file for rakudo and added it to the list of files to run (so we can tell when this feature is working) -- |
From @cokeOn Sat Feb 22 17:33:28 2014, coke wrote:
-- |
From @tadzik"( ͡° �� ͡°)".chars on Rakudo (all 3 backends, as of today) returns 11, |
From @masak<lelf> Is \w defined as <alnum> on purpose? |
From [Unknown Contact. See original ticket]<lelf> Is \w defined as <alnum> on purpose? |
From @jnthnOn Mon Apr 27 05:47:38 2009, helmut@wollmersdorfer.at wrote:
The test cases associated with this ticket are now passing on Rakudo on MoarVM, along with many, many other NFG-related tests. I'll resolve this catch-all ticket, and we can open more specific ones for particular NFG-related issues that crop up. |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#65170 (status was 'resolved')
Searchable as RT65170$
The text was updated successfully, but these errors were encountered: