Posted by Christoph Thiede on Aug 19, 2021; 6:09pm
URL: https://forum.world.st/The-Trunk-Collections-pre-857-mcz-tp5104939p5130661.html

Hi all,

two years later, I still would love to see Patrick's proposal being accepted in the Trunk.

My concrete problem with SOH (start of header) not being in Character separators is that text anchors in Smalltalk source code currently mix up the Shout styler, which is due to the send to CharacterSet nonSeparators from SHParserST80 scanWhitespace. Now one might argue that we could introduce a separate CharacterSet notAtAllSeparators/nonUnicodeSeparator autc. (which would also exclude SOH), but I would rather dislike this proposal because it would force us to maintain multiple different definitions of the term "character" and increase the overall domain complexity. I can't see what would be wrong with treating all character instances according to the Unicode standard (as other frameworks such as .NET seem to do, too).

I have been using Dave's version of Character separators from above for the latest months and I did not experience any unintended side effects of the change.

Could we please integrate Patrick's change, or are there any major objections? It would be great to get this kind of stuff working in Babylonian & Co. :-)

Best,
Christoph

PS: See also: http://forum.world.st/ENH-isSeparator-td5129517.html