Re: [gobo-eiffel-develop] UC_STRING is XML parser output

[Berend de B. <be...@po...>]

Eric Bezault <gob...@if...> writes:

> (so make sure to explicitly create it now), and UC_STRING
> is now deferred. It currently has one concrete descendant,
> UC_UTF8_STRING, but implementations based on 16 ad 32 bits
> will follow. Unless you explicitly want to create a UTF-8

Is this a good design? IMO there is just one class UC_STRING, and you
have different storage classes (UTF8/16/etc), and you can
change/optimize them on the fly.

Or is this also related to the workaround?

-- 
Live long and prosper,

Berend de Boer