Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63283
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain planetavent.de from 89.107.189.172 cause and error)
MIME-Version: 1.0
Date: Mon, 8 Oct 2012 18:14:20 +0200
Message-ID: <CAOg_pRTo3_E6CJ_b6BBT4ZkKxEgaUXs67VeahbWdUStcxbneZQ@mail.gmail.com>
To: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: stream_get_line behaviour Bug #63240
From: scope@planetavent.de (Nicolai Scheer)

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