Re: Strange crash on custom iterator

[Lucretia <laguest9000@googlemail.com>]

On Wednesday, 4 July 2018 15:37:40 UTC+1, Dan'l Miller  wrote:

> The difficulty is that •no one• has the single •solution• for this problem or these concomitant problems.  Not even J-P. Rosen is a possessor of complete solution in his Wide_Wide_String recommendation, because his replies seem to factually-incorrectly imply that there exists a fully-normalized single-codepoint character in Unicode/ISO10646 for each grapheme/letter.

JP Rosen told me to go read the AI on the matter, which I did. He states they talked about it, there's not much talking in the AI at all! Bob Dewar states they shouldn't really abuse the *String types by subtyping and does exactly that by introducing a package he wrote to handle UTF using those subtypes. The rest of the AI is about how to fit that into the standard.

Back then, they should've chosen the Unicode standard over the ISO10646 as it's freely available, yes the encodings are interchangeable, but that's not really the point. 

They should've decided to obsolete the current mess, the same way they did with ASCII and made String and Unbounded_String UTF-8 encoded. They could still have the old latin based strings as compatibility types. They should've made all source be encoded the same way, which they did anyway for the iso spec.

Then defined a bunch of iterators for the types based on code points, grapheme clusters, word/line boundaries, bidi, etc.

Then taken out all references to characters as that concept isn't really applicable to Unicode as a "character" can be one or more code points.