stream_get_line behaviour Bug #63240
| From: | Nicolai Scheer | Date: | Mon, 08 Oct 2012 16:14:20 +0000 |
| Subject: | stream_get_line behaviour Bug #63240 | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-63283@lists.php.net to get a copy of this message | ||
Hi!
We switched from php 5.3.10 to 5.3.17 this weekend and stumbled upon a
behaviour of stream_get_line that is most likely a bug and breaks a
lot of our file processing code.
The issue seems to have been introduced from 5.3.10 to 5.3.11.
I opened a bug report: #63240.
The issue seems to be related to #44607, but that one got fixed years ago.
Is anybody able to confirm this behaviour or has stumbled upon this?
Furthermore the behaviour of stream_get_line on an empty file seems to
have changed between php 5.3.10 and php 5.3.11:
<?php
$file = __DIR__ . 'empty.txt';
file_put_contents( $file, '' );
$fh = fopen( $file, 'rb' );
$data = stream_get_line( $fh, 4096 );
var_dump( $data );
result in
string(0) ""
for php 5.3.10
and in
bool(false)
for php > 5.3.10.
I don't know if this should be considered a bug, but as far as I know
such a behaviour should not change during minor releases...
Any insight is appreciated!
Greetings
Nico