Thanks for the help.
I do agree with Paul that something should be mentioned in the substr
documentation.
David Santiago
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Because Str is treated as a set of graphemes, and "\r\n" is treated as a single
character, .substr() is doing the right thing here.
If you really want to treat it as a series of codepoints, you may want to go
through Blob/Buf to get there:
> "1234\r\n78".encode.subbuf(*-4)
utf8:0x<0D 0A
Unicode conformance requires "\r\n" to be interpreted as \n alone.
With that said; no, I don't not know how to turn this off.
I personally think I'd consider this a bug. If not a bug, greater
documentation efforts that explain this.
The display routines (say / print) don't modify the string on ou
A 10 de fevereiro de 2020 16:57:55 CET, David Santiago
escreveu:
>
>
>Hi!
>
>Is there a way to change the the following behaviour, so it considers \r\n as
>two characters when using substr, instead of one?
>
>On raku version 2019.11
>
>> "1234\r\n". substr(*-4)
>4
>78
>> "1234\r\n". substr(*-4).
Hi!
Is there a way to change the the following behaviour, so it considers \r\n as
two characters when using substr, instead of one?
On raku version 2019.11
> "1234\r\n". substr(*-4)
4
78
> "1234\r\n". substr(*-4).ords()
(52 13 10 55 56)
Best regards,
David Santiago
--
Sent from my Androi
