Re: [Squeak-VMdev] Versiojn 4 changes

[Yoshiki O. <Yos...@ac...>]

  Ned,

> That's not the case unless you have decided on a standard encoding. For 
> instance, if you load Ian's X11 Fonts package into a stock image, you will 
> have fonts that display the same Character as different glyphs, because the 
> fonts in the stock image use the MacRoman encoding, and the X11 fonts use 
> Latin-1.

  Oh.  I completely assume that we move to Unicode based encoding,
Which means that first 256 chars are compatible latin-1.

> >   To which point?  We should go with 24 bit immediate?  We should go
> > with "naked code point + attributes" approach?
> 
> I think that we should probably stick to 24 bits and put other information 
> into the Strings.

  It is going to be a little bit more intrusive change than we might
want to.  The Compiler should carry the attributes from the thing it
evaluates to the result.  For example, if you put a string in a
workscape something like:

  dict at: ',' put: ','

and put the different language tag to the second comma from the first
in the workspace.  In that case, the commas look differently in the
workspace.

  If you do-it the expression, you want to make the key and value in
the dictionary carry the same attribute when *they* were in the
workscape.  The self-containedness is nice in this regard.

  But, what would be the best argument to make the wide-characters
immediate objects?

-- Yoshiki