on 6/30/04 10:46 AM, Joseph J. Strout at joe at realsoftware dot com wrote:
> At 10:40 AM -0400 6/30/04, Phil Heycock wrote:
>
>>> And when you do this, the resulting file appears different when
>> viewed as hex?
>> Yes
>
> Hi Phil,
>
> All right, you've piqued my curiosity. Please send me your test
> project along with the two binary files (with and without the memory
> block work-around) that it created on your machine, and details about
> what exactly your machine (operating system) is and what version of
> RB you're using. I want to get to the bottom of this.
>
> Thanks,
> - Joe
**********************************************************
My 'yes' was a mistake. I was looking at the wrong file when I responded.
As suggested, the answer lies in the way that BBEdit displays the file via
'hex dump', not in RB. The files are identical. If I had been looking at the
files with HexEdit from the beginning, there would never have been an issue.
I was misled by BBEdit's hex dump presentation.
Never mind.
(Actually... thanks to all who responded. Very helpful. Sorry to have
alarmed anyone unnecessarily.)
PWH
***********************************************************
>Great! I knew there had to be something like that going on.
>Since this message came directly to me, you might want to post an
>explanation to the NUG in case there are others there growing
>concerned about whether the BinaryStream works properly (and also for
>people in the future who run across this thread in the archives).
*******************************************************************
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|