> Floats are written in "native" endianness (the natural endianness of
> the machine writing the file), but along with a flag telling which
> endianness is used.

Ouch!  That will teach me to read only one piece of code.  My common
work usually has me dealing with standardized network representations,
so I missed this strategy completely.  [Chris sticks head in bucket.]

> > Harder, does anyone have any good ideas besides conversion to

> The next release of OCaml will use the same format for float arrays in
> native-code and in bytecode, thus solving this problem.

Both compact I hope.  Any idea on when this might happen?

-- 
Christopher Oliver                     Traverse Internet
Systems Coordinator                    223 Grandview Pkwy, Suite 108
oliver@traverse.net                    Traverse City, Michigan, 49684
let magic f = fun x -> x and more_magic n f = fun x -> f ((n f) x);;