X-Spam-Check-By: sourceware.org
Message-ID: <85a409ca0605211855r63e15d59o3db1f55e3a321be2@mail.gmail.com>
Date: Mon, 22 May 2006 13:55:24 +1200
From: "Paul Dorman" <paul DOT dorman AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Reading Term::ReadKey support for ActiveState Perl and Cygwin
In-Reply-To: <Pine.GSO.4.63.0605212133300.21697@access1.cims.nyu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Disposition: inline
References: <85a409ca0605211622q7acb3708v897b20652c7c31d0 AT mail DOT gmail DOT com> 	 <Pine DOT GSO DOT 4 DOT 63 DOT 0605212133300 DOT 21697 AT access1 DOT cims DOT nyu DOT edu>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k4M1tZff016239

Yes, I've done some more research and experimentation and determined
the lack of STDIN and STOUT in Cygwin makes it impossible to do what I
would like with ActiveState Perl. I don't mind Cygwin Perl at all, but
here we must use the ActiveState implementation (by policy).

Is this situation likely to improve in the future? Could a real
terminal be created for Cygwin complete with STDIN and STDOUT? I
imagine it's a pretty difficult thing to implement...

Thanks for your reply.

Rgds,
Paul

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/