Jan. 18, 2019
1:38 p.m.
On 18 Jan 2019, at 14:23, Guillermo Polito <guillermopolito@gmail.com> wrote:
I think that will just overcomplicate things. Right now, all Strings in Pharo are unicode strings. Characters are represented with their corresponding unicode codepoint. If all characters in a string have codepoints < 256 then they are just stored in a bytestring. Otherwise they are WideStrings.
I think assuming a single representation for strings, and then encode when interacting with external apps/APIs is MUCH simpler.
Absolutely ! (and yes I know that for outgoing FFI calls that might mean a UTF-8 encoding step, so be it).