> > 
> >   It will, but it will anyway if you choose an internal representaion
> > other than today's String, which you will need to do anyway.
> 
>   This may require a bit more clarification...  I don't know what is
> in that 90MB image, but if you rewrite your code a bit, probably
> changing the test against "String" to "AbstractString" your code may
> well work fine (or maybe not.)  Even for that kind of meta-level
> program, the change should be pretty small.
> 
>   I actually don't understand what you meant by "stops loading,"
> though.  Are you worrying about the image won't run on a (new) VM?
> Then, you really don't have to worry about it.
> 

I don't understand, then.  What happens if the VM says "This VM uses
encoding timbuktu-3-rot11" and my image doesn't know about this
encoding?  I thought the proposal was that the VM specifies a character
encoding to use, and the image is expected to support that encoding.


Lex