From: Ned K. <ne...@bi...> - 2004-04-07 05:28:54
|
On Tuesday 06 April 2004 8:40 pm, Yoshiki Ohshima wrote: > =A0An extreme along this line is that we even don't need Character > objects; we can make a string with length of 1 behave as if today's > character. =A0After all, "a character cannot print itself" is the way > Unicode is designed. =A0So, using Unicode is kind of a synonym of this > approach. =A0(I wouldn't pursue this extreme in Squeak, though.) > > =A0 The other approach is to make a character self-contained thing. =A0It > knows how to print itself, etc. =A0To make this happen, a Character has > to carry more than naked code-point and the higher bits in the word is > where it goes. But we already have this situation with the existing Characters. They don't= =20 know their encoding, so any attempt at printing them in an Inspector is ver= y=20 possibly wrong (unless they're in the default encoding). How often do you find yourself inspecting individual Characters inside a=20 String? Even more to the point: how often do you find yourself inspecting Character= s=20 that aren't inside a String? After all, a String could provide the required context to inspect its=20 characters. =2D-=20 Ned Konz http://bike-nomad.com GPG key ID: BEEA7EFE |