Bug #13832 Updated: fseek() offset problem with Win32 newlines
ID: 13832
Updated by: ssb
Reported By: ryan@footboot.net
Old Status: Open
Status: Bogus
Bug Type: Filesystem function related
Operating System: Windows 2000 Professional
PHP Version: 4.0.6
New Comment:
Markus says it's bogus
Previous Comments:
------------------------------------------------------------------------
[2001-10-25 21:44:22] ryan@footboot.net
This bug is probably related to bug number #6023 ("Problem with either fgets or ftell in
ISAPI")
------------------------------------------------------------------------
[2001-10-25 21:42:00] ryan@footboot.net
Note: this still occurs in 4.0.6 (I think they're the same bug)
What I did: tried to read over a file backwards using fseek().
What should have happened: I should be able to create an array of the last few lines of a file,
without reading the whole file.
What did happen: for every newline fseek()ed over fread() seemed to gain a byte.
I believe this could be a problem with the way fseek() handles new lines in Win32 (possibly not
always). fread() seems to read Win32 newlines as one byte, while fseek() reads them as two.
In the following example, if the file has no newlines or the newlines are in Unix format, $buf is
identical. If there are Win32 newlines, it isn't.
<example>
$fp = fopen('/temp/newline.txt', 'r');
fread($fp, 5);
$buf = fread($fp, 5);
fclose($fp);
$fp = fopen('/temp/newline.txt', 'r');
fseek($fp, 5);
$buf = fread($fp, 5);
fclose($fp);
</example>
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=13832&edit=1
Thread (4 messages)