Re: Is Bug #34972 (no non-blocking on STDIN on Windows) going to be fixed?
| From: | Pierre Joye | Date: | Fri, 09 Dec 2011 01:21:46 +0000 |
| Subject: | Re: Is Bug #34972 (no non-blocking on STDIN on Windows) going to be fixed? | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-56852@lists.php.net to get a copy of this message | ||
The usage is very limited as well, for STDIN that is. For other
streams, non blocking works perfectly. Also last time I checked it was
not possible to do it without some heavy changes, it can't be done in
5.3 or 5.4 as of now (respectively stable and release candidate
phases).
I'd to say that async IO, event and other similar things are much
higher in my todos list.
On Fri, Dec 9, 2011 at 1:58 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> It is non-trivial to implement on Windows. It is more of a feature request than a bug. UNIX
> supports non-blocking stdin natively, Windows doesn't. A Windows guy would need to write a
> compatibility layer to get this to work and we don't have very many Windows guys around.
>
> -Rasmus
>
> On Dec 8, 2011, at 4:34 PM, Jonathan Chan <jnthan.chan@gmail.com> wrote:
>
>> Hello,
>>
>> Is there any intention to fix Bug #34972
>> (https://bugs.php.net/bug.php?id=34972)? It was first submitted six
>> years ago, but the bug still seems to exist.
>>
>> Thanks.
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org