Re: Value/Location

[Andrew Cagney <cagney@redhat.com>]

Yes,

Every time I tried to get frysk.value.Format to use the type's 
byte-order I'd get test-suite failures caused by another case of this.  
The underling problem is that type code used to read/write byte-order 
dependent values wasn't explicitly specifying the type's required 
byte-order.

Hopefully the last of these get flushed out with the next few commits.

Andrew

Stan Cox wrote:
> The frysk.value constructor (Type type, String textFIXME)  
> ->calls (new Location(type.getSize())  
>   ->calls new ArrayByteBuffer(capacity) 
>     which will assume a big endian buffer
>
> One possibility is to have Value do:
> abb = new ArrayByteBuffer (..);
> abb.order(type.endian); 
> Location(abb)
>
>
>
>