Notes |
|
|
This is correct behaviour when reading files in text mode. Byte 0x1A marks the end of file. |
|
|
|
I hope to see support for reading binary functions in the future (whether this function or a new function). |
|
|
(0001519)
|
Falcon
|
2012-05-24 20:47
|
|
Read status must stay binary unsafe due to fact that it converts line endings to CRLF so that they have alway same form in the script.
The only solution would be to add new, binary safe function. |
|
|
|
A new function that can read files binary-safely would be a sufficient solution. For the function name... ReadFileBinary, ReadFileBin, ReadFileB? 'Bin' keeps the overall function name not too long, and yet still more descriptive than simply 'B'.
Another option would be having a collection functions with similar behavior to fopen, fread, fwrite, fclose, fseek, etc. or similar. The user has the choice here to specify read/write/both, binary/non-binary, create (or not to) file if non-existent, specify write location (append/replace from scratch), etc. This may introduce additional features.
When writing this, I was referring to:
http://us3.php.net/manual/en/function.fopen.php [^]
http://msdn.microsoft.com/en-us/library/y973b725.aspx [^] (and links there-within) |
|
|
|
If you have requests for features please use the forums instead.
The bugtracker is only for bugfixes. |
|
|
(0001577)
|
Falcon
|
2012-08-23 21:18
|
|
since many scripts rely on readfile's line ending conversion, this function cannot be modified to read binary files. |
|