X-Spam-Check-By: sourceware.org
Date: Sun, 21 May 2006 22:09:12 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Paul Dorman <paul DOT dorman AT gmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Reading Term::ReadKey support for ActiveState Perl and Cygwin
In-Reply-To: <85a409ca0605211855r63e15d59o3db1f55e3a321be2@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.0605212202020.21697@access1.cims.nyu.edu>
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>  <85a409ca0605211855r63e15d59o3db1f55e3a321be2 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Mon, 22 May 2006, Paul Dorman wrote:

> 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.

Huh?  Cygwin does have STDIN and STDOUT -- they are just not bound to a
console, and ActivePerl doesn't like that.

> I don't mind Cygwin Perl at all, but here we must use the
> ActiveState implementation (by policy).

And what would the crucial difference be between an ActiveState
implementation's behavior and Cygwin's?  I mean, can't you simply run
the Perl script using Cygwin's perl?  Then you get the best of both
worlds...

> 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...

Most likely not -- Cygwin uses ptys (pipes, essentially) to simulate ttys
for processes that can't be bound to a Windows console, and there may be
real restrictions (e.g., Windows limitations) for not being able to
implement what you're asking for without breaking existing Cygwin
functionality.  However, if it is really important to your company, you
can try looking into funding some research on this (either via a Cygwin
support contract with Red Hat, or via direct donations to a private
developer).
HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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/