X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Subject:	Re: _kbhit
Date:	Mon, 13 Feb 2006 12:10:25 -0500
Message-ID:	<6CA15ADD82E5724F88CB53D50E61C9AE9ECE5F@cgcmail.cgc.cpmc.columbia.edu>
From:	"Michiel De Hoon" <mdehoon AT c2b2 DOT columbia DOT edu>
To:	<cygwin AT cygwin DOT com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id k1DHAY3e002198

Gary R. Van Sickle wrote:
> > First, some Cygwin programs will need _kbhit to be 
> > able to interact with the Windows OS.
> 
> That's simply not true.  They may *want* it so that they can interact with
> cmd.exe, in which case they're not a "Cygwin program".

If:
1) A program needs to run a Windows message loop;
2) This message loop should be exited when user input is available on stdin;
3) The program needs to link to cygwin1.dll;
then it is a Cygwin program that needs _kbhit (either present in the DLL or
implemented by myself using select()), isn't it?

--Michiel.

Michiel de Hoon
Center for Computational Biology and Bioinformatics
Columbia University
1150 St Nicholas Avenue
New York, NY 10032


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

- Raw text -