Image portabilty problem due to load-time String mapping
GBS creates global class mappings for Strings based on the
appropriate string class for the platform upon which the client
image is currently running. So loading GBS into a VisualWorks image
will map the appropriate string class to the GemStone class ISOLatin,
a subclass of String. However, if this image is saved, and started
up on a different platform with a different string class (such as
Windows to Unix) strings will not map correctly.