Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56852 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52869 invoked from network); 9 Dec 2011 01:21:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Dec 2011 01:21:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:59748] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2C/00-52495-EA261EE4 for ; Thu, 08 Dec 2011 20:21:50 -0500 Received: by ghbg16 with SMTP id g16so2256125ghb.29 for ; Thu, 08 Dec 2011 17:21:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=y6qkrP6Wjkz+UsJqMGD1JWolRc+fr0pkak814H1rk+0=; b=UQ8BTAf7+s46QaTv6qexUwVNYUrGxx2cCYmGqkHqzh3eOj7h7ywy5kOThTchP068ks WpOtcjUkGX2/uHwsfn4wnPwnc99CHdCP2PU83gqcH5lLeL3I/ghDbPOq19YhiGjf5YYX 6kVy1GboqbInOhgZHXzAVn+fu+0ck9D8RLDbc= MIME-Version: 1.0 Received: by 10.236.138.131 with SMTP id a3mr4581505yhj.101.1323393707071; Thu, 08 Dec 2011 17:21:47 -0800 (PST) Received: by 10.146.204.6 with HTTP; Thu, 8 Dec 2011 17:21:46 -0800 (PST) In-Reply-To: References: Date: Fri, 9 Dec 2011 02:21:46 +0100 Message-ID: To: Rasmus Lerdorf Cc: Jonathan Chan , "internals@lists.php.net" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Is Bug #34972 (no non-blocking on STDIN on Windows) going to be fixed? From: pierre.php@gmail.com (Pierre Joye) 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 wrote: > It is non-trivial to implement on Windows. It is more of a feature reques= t 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 wrote: > >> Hello, >> >> Is there any intention to fix Bug #34972 >> (https://bugs.php.net/bug.php?id=3D34972)? 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 > --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org