Re: Unicode implementation concept

The number of programming languages that support string
slicing is evidence enough of its utility.  I should not
have to invent scenarios.  Examples include Python,
Icon, JavaScript, SML, Perl, ad infinitum.

Well, here is a scenario anyway.  Consider single
character replacement.  This operation entails a
performance hit using serial storage.  When a wide char
is replaced by a normal char, a block copy is required
to retain serial format, correct?  The proposed scheme
obviates the need for such block moves.

It was stipulated up front that I consider the
designer's performance concerns overblown, but I wish to
address them at the level that concerns him.  If his
motivations are not clear I apologize.  Anyone still
confused, please ignore this thread, but do not attempt
to cut it short.  It looks to me like the list traffic
is small anyway.

I am interested in hearing from other people on the
list.  Specifically, I would like to hear about test
suites, test data, or test scenarios should I implement
this concept.  If I do then I will report back with code
in hand.

Thanks again,

Mark