Date: Mon, 13 Feb 2006 12:18:31 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: _kbhit
Message-ID: <20060213171831.GC7865@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
References: <6CA15ADD82E5724F88CB53D50E61C9AE9ECE5F@cgcmail.cgc.cpmc.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6CA15ADD82E5724F88CB53D50E61C9AE9ECE5F@cgcmail.cgc.cpmc.columbia.edu>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mon, Feb 13, 2006 at 12:10:25PM -0500, Michiel De Hoon wrote:
>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?

Please go back and read the first few sentences at the cygwin web site.
When you do that, you'll note that this project is not intended to offer
the Windows API to programs.

Please stop arguing about this.  As much as you may want this, it's not
going to happen.

cgf

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