Re: Strange crash on custom iterator

[Shark8 <onewingedshark@gmail.com>]

On Thursday, July 5, 2018 at 11:20:00 AM UTC-6, Dan'l Miller wrote:
> 
> But, Shark8, you seem to criticizing something a little different than that.  In some alternate universe where Unicode or ISO10646 transpired entirely differently, what would Unicode-done-right* look like, especially w.r.t. Ada strings.  It seems that you are alluding to some sort of multiple-strand string or something like that (not merely allocating the billion nonBMP codepoints better so that we would have a one-letter-one-codepoint axiom). 

Well, Ada does like 'disassembling' things [concepts, etc] into usable component pieces, traditionally-speaking. So, I'd expect the multilingual problem-space would likely be decomposed into some usable/useful sets of types/subprograms.

To borrow from other ISO stuff, perhaps something like:

-- ISO 639-1
PACKAGE LANGUAGES IS
  Type Code is ( ab, aa, [...], za, zu );
  -- other stuff.
END LANGUAGES;

PACKAGE LANGUAGES.CONSTRUCTS IS
   -- A Text is a full sequence of linguistically meaningful data, a sequence of contexts.
   Type Text is private;
   -- subprograms...
   
   -- Essentailly a "string" w/ a language context.
   Type Context( Language : Code; Length : Natural ) is private;
   -- subprograms
PRIVATE
  --...
END LANGUAGES.CONSTRUCTS;

Or something; the point is the preservation of the structure/context of the sequence-of-symbols\words\graphemes\whatever to provide a solid multilingual foundation rather than throwing away all context, shoving everything in the Unicode-blender and having to deal with string-of-hexadecimal-sludge (codepoints) which, in-turn, forces reconstruction of the lost structures and contexts... maybe involving the [ab]use of RegEx, that always seems to be an answer when dealing with textually-represented data, hence why so many of our peers seem to think that RegEx is suitable for parsing/processing HTML....

Yes, it bucks the "everything is a string" mentality of C/unix influenced OS-APIs; where the analog of a path would be an actual vector of names [eg ("root", "projects", "source", "file.adb")] rather than a plain text-string [eg "root\projects\source\file.adb"] if applied to the OS as well.

The whole purpose is, as stated up-thread, "to aid the creative craftsman, not enforce mediocrity".