[M3devel] Do we really want to truncate wide chars?

[Rodney M. Bates]

Right now, the implementations of Text.GetChar and Text.SetChars that we got with
cm3, silently truncate any of the requested characters whose value won't fit in
the range of CHAR.  Do we really want this behavior?  Is there any existing code
that depends on it?  I can't imagine a case where client code would want this.

I propose we change it to either give a checked runtime error or raise an
explicitly declared exception, if the value won't fit in a CHAR.

Any thoughts?