Bug in Utilities`BinaryFiles`
- To: mathgroup at smc.vnet.net
- Subject: [mg15746] Bug in Utilities`BinaryFiles`
- From: Brett Patterson <Brett.Patterson at durham.ac.uk>
- Date: Fri, 5 Feb 1999 03:42:42 -0500 (EST)
- Organization: University of Durham
- Sender: owner-wri-mathgroup at wolfram.com
There seems to be a bug, or omission in the package
The option ByteOrder defaults to MostSignificantByteFirst, however on a
DEC Alpha (Digital Unix), the byte order is LSB. The ByteOrder
functionality seems to be absent in all the Read functions (e.g.
ReadListBinary), so that
ReadListBinary[filename, Single, ByteOrder->LeastSignificantByteFirst]
produces identical garbage to
ReadListBinary[filename, Single, ByteOrder->MostSignificantByteFirst].
Note that the functionality works with Integers. Why is this not working
I've looked at the package code, and the functionality for LSB/MSB
appears to be missing.
Dr Brett A. Patterson Room 148 Astronomical
Instrumentation Group Tel: +44 191 374 2105 Department of Physics
Fax: +44 191 374 3749 University of Durham
mailto:Brett.Patterson at durham.ac.uk South Road, Durham DH1 3LE, UK
Prev by Date:
Q: how to list vertices of the Geodesate of a polyhedron?
Next by Date:
Re: Help to clarify 'Map', 'Apply', and 'Thread'.
Previous by thread:
Re: Q: how to list vertices of the Geodesate of a polyhedron?
Next by thread:
Re: a tricky limit