I'm reading a binary file a character at a time and looking for the
end-of-file marker so I know when to stop reading but the read terminates
before the entire file is read. There seems to be an eof marker in the
file that is not at the end of the file. CharToNum(EOF) returns a 4
which
On 18/9/00 4:45 pm, James Parker [EMAIL PROTECTED] wrote:
I'm reading a binary file a character at a time and looking for the
end-of-file marker so I know when to stop reading but the read terminates
before the entire file is read. There seems to be an eof marker in the
file
On 18/9/00 4:45 pm, James Parker [EMAIL PROTECTED] wrote:
I'm reading a binary file a character at a time and looking for the
end-of-file marker so I know when to stop reading but the read terminates
before the entire file is read. There seems to be an eof marker in the
file
to be an eof marker in the
file that is not at the end of the file. CharToNum(EOF) returns a 4
which could appear at places other than the end of the file, right?
Is the following correct?
repeat forever
read from file sourcefile for 1 character
if the result is "eof"
the entire file is read. There seems to be an eof marker in the
file that is not at the end of the file. CharToNum(EOF) returns a 4
which could appear at places other than the end of the file, right?
Is the following correct?
repeat forever
read from file sourcefile for 1 character
quot;read until eof", it just saves a
couple of lines of script for opening and closing the file. Same
I must say "put url" has been my favourite command dealing with files.
However, I am planning to use the more traditional "open" and "seek" command
to dea
.
Is this applicable to all MetaCard disk I/O commands on Mac, or just
effecting:
put url "binfile:thefile.txt"
where it really reads the entire file into RAM?
That, and "read ... until eof" both read the whole file into RAM,
which means you need to have enough.
This is fun
