You wrote in your plans about Unicode support:
"Internal representation of Unicode (image and VM)
-
In the image, we need new classes to represent UTF-8 and WideCharacter (UTF-16) data (subclasses of EsString and others)
"
After now working with ICU over the last days I would say, that we should have DBCharacter (two bytes - which actually is the implementation of Character) and QBCharacter (4 bytes).
I'm now working on the streaming support of ICU on Unicode streams and there one has instances of characters, which are 4
bytes long.
By the way - where do instances of the class Character (internally) store their "value" ????
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To post to this group, send email to
[hidden email].
To unsubscribe from this group, send email to
[hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
Locked
