>> Incidentally, can you change binStream.LittleEndian on-the-fly, while >> the stream is open? > > Yes (AFAIK) it's just a flag that the read/write methods check. Don't > expect any magic from LittleEndian properties though - you can't set > the flag then write out a big chunk of data and expect it to be > correct. You have to use individual accessors (long, single etc.). > LittleEndian doesn't change the underlying memory, it's only a hint > to the accessor/read/write methods that certain return values should > be swapped.
I've been following this with some interest because I've been working on memoryblocks for a long time. And of course, like others I have an Intel now so things have changed slightly. I really liked the idea of the word/long read functions based the processor and I think I will implement those in future. Once again, I got some great ideas from the group! Mel _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
