ID: 34972
Updated by: [EMAIL PROTECTED]
Reported By: VJTD3 at VJTD3 dot com
Status: Open
Bug Type: Streams related
Operating System: *
-PHP Version: 5.1CVS-2006-03-27
+PHP Version: 5.2.4
Assigned To: wez
New Comment:
VJTD3 at VJTD3 dot com reported:
The problem still exists in version 5.2.4 of php.
Previous Comments:
------------------------------------------------------------------------
[2007-09-06 12:04:51] VJTD3 at VJTD3 dot com
re: julian
It's not that people "don't" it's that they can't when the bug prevents
some most basic functionality. If the bug was fixed this method of
functionality would be viable and then more prevalent compared to python
or perl script counterparts of same design since php is easier to
develop with and use then perl, python, and similar types for the same
functionality.
re: [EMAIL PROTECTED]
The number came from the CVS page, it was not "invented" by me. Pick a
version convention and stick with it everywhere. People use php and find
bugs. if you make it difficult with several naming conventions your
going to have issues. The reality is a person shamed php into looking
into the ticket again, clearly when you replied 17 Jul 2:28pm UTC it was
not lost not to mention all messages before that. If there was an error
any past maintainer of the bug report including you should have
addressed it. Don't blame me for you not doing your role. You know your
bug reporting tools significantly better then any outsider. Not to
mention you/the assigned person is notified of replies. Don't scape goat
using the reporter of the bug for people not doing their role. Thank
you.
The problem still exists in version 5.2.4 of php.
------------------------------------------------------------------------
[2007-09-05 14:00:11] [EMAIL PROTECTED]
Fixed invalid version number. Does this problem exist with PHP 5.2.4?
Note: Due to the invalid version number this report was lost.
Please don't invent your own versions, the first char in the version
field is supposed to be the major version number!
------------------------------------------------------------------------
[2007-08-23 15:53:20] julian at precisium dot com dot au
I'm having this problem on Vista x64 with PHP 5.2.3.
This is a real showstopper for certain types of CLI app - people can't
always be waiting for newlines or eofs to read their data.
I don't mean to be rude but I'm kinda shocked such a major bug has been
unaddressed for nearly 2 years. I guess it just means people aren't
really using PHP for CLI apps on the windows platform.
------------------------------------------------------------------------
[2007-08-19 20:51:34] donnyk at gmail dot com
i also have the same problem, i've tried the latest snapshot on windows
to no avail. It works on my linux systems however.
------------------------------------------------------------------------
[2007-08-10 13:01:48] VJTD3 at VJTD3 dot com
<?php
stream_set_blocking(STDIN, FALSE);
echo fread(STDIN, 10);
?>
notice how it just sits there? (blocking) it should exit instantly with
a null echo. (same as a tcp connection where if you just do a read that
is too fast with nonblocking it never gets a chance to fetch the data.)
what is happening is that php is blocking waiting for input
(specifically enter (line ending))
problem:
if you are echoing debug information and want to use key functionality
in tandem you can't because everything is blocked till you hit enter.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/34972
--
Edit this bug report at http://bugs.php.net/?id=34972&edit=1
