Experimental Physics and
Industrial Control System

Jeff Hill <[email protected]> · Wed, 02 Mar 2005 16:35:32 -0700

> -----Original Message-----
> From: Benjamin Franksen [mailto:[email protected]] > 
> 
> On Wednesday 02 March 2005 22:02, Jeff Hill wrote:
> > My solution to the wide character issue was to have the
putChar
> > and getChar interfaces pass type int. UTF-8 then becomes an
> > implementation (an internal storage compression) issue.
> 
> Ok, this is a possibility. But it means that, for instance, 
> an IOC will use wide characters throughout its code. Just 
> caring about our precious memory, you know... ;) That is, 
> provided it doesn't want to re-encode everything 
> again, of course...
> 

The stringSegment interface requires only that internal string
tokens 
can be converted to a int sized universal code only when getChar 
and putChar are called, but there is no requirement that the 
implemenation use an internal storage of size int.

The getChar interface will be used in one character at
a time situations where the storage overhead of an int can be
safely 
neglected. Otherwise if there are any multi-token segments being
stored 
they would only be stored in an implementation defined format
accessed 
through the stringSegment interface. Anyways, that is the
standard 
dataAccess approach: interface to data, but do not specify a
storage 
format.

Jeff

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System