RE: _kbhit

2006-02-18 Thread Gary R. Van Sickle
> From: Shankar Unni > Sent: Friday, February 17, 2006 2:28 PM > To: cygwin@cygwin.com > Subject: Re: _kbhit > > Gary R. Van Sickle wrote: > > > Arend-Jan Westhoff writes: > >> I cannot confirm your assertion that msvcrt.dll and cygwin1.dll > >

Re: _kbhit

2006-02-17 Thread Christopher Faylor
er >:-). > >The problem is that, for instance, some of your malloc calls will link >to the cygwin libc, while others (from within the Windows DLLs) will >link to MSVCRT, and if you free the pointer with the "other" library, >terrible things will happen. Details, details. Th

Re: _kbhit

2006-02-17 Thread Shankar Unni
Gary R. Van Sickle wrote: > Arend-Jan Westhoff writes: I cannot confirm your assertion that msvcrt.dll and cygwin1.dll cannot be used together. The Gary Exclusion Principle: Two C runtimes cannot occupy the same point in space at the same moment in time. The problem here is that unfortu

RE: _kbhit

2006-02-15 Thread Gary R. Van Sickle
d bash on CMD but not > on rxvt; as stated elsewhere in this thread the Microsoft > _kbhit is not very good). > > HTH, > > Arend-Jan Westhoff. The Gary Exclusion Principle: Two C runtimes cannot occupy the same point in space at the same moment in time. A corollary to that:

Re: _kbhit

2006-02-15 Thread Arend-Jan Westhoff
At 18:58 2006-02-10 -0500, Michiel de Hoon wrote: >> On Sun, Feb 05, 2006 at 01:17:33PM -0500, Michiel De Hoon wrote: >> >For one of my software projects, I need the _kbhit function to check the >> >console for keyboard input. While this function is present in msvcrt.dll,

RE: _kbhit

2006-02-13 Thread skaller
On Mon, 2006-02-13 at 18:11 +, Dave Korn wrote: > Why would any app (in general, and yours in particular) /need/ to link to > cygwin1.dll? The only reason is for the POSIX/Unix/Linux compatibility it > provides, because that is _all_ that cygwin1.dll does. It is quite possible this need ar

RE: _kbhit

2006-02-13 Thread Dave Korn
On 13 February 2006 17:10, 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 &

Re: _kbhit

2006-02-13 Thread Christopher Faylor
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 i

Re: _kbhit

2006-02-13 Thread Michiel De Hoon
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 progra

RE: _kbhit

2006-02-10 Thread Gary R. Van Sickle
> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Michiel De Hoon > Sent: Friday, February 10, 2006 5:58 PM > To: cygwin@cygwin.com > Subject: Re: _kbhit > > > On Sun, Feb 05, 2006 at 01:17:33PM -0500, Michiel De Hoon wrote: > > >For one of

Re: _kbhit

2006-02-10 Thread Michiel De Hoon
> On Sun, Feb 05, 2006 at 01:17:33PM -0500, Michiel De Hoon wrote: > >For one of my software projects, I need the _kbhit function to check the > >console for keyboard input. While this function is present in msvcrt.dll, it > >is missing from cygwin1.dll, so I started writing

Re: _kbhit & memory leak in select()

2006-02-10 Thread Michiel De Hoon
> On Feb 5 13:17, Michiel De Hoon wrote: > > 1) Where is the select_record deleted? The select_stuff variable sel will be > > gone after we exit cygwin_select, and with it the pointer to the > > select_record we allocated in select_read. > > In the select_stuff destructor. Ha. You're right. I gue

Re: _kbhit & memory leak in select()

2006-02-05 Thread Christopher Faylor
On Sun, Feb 05, 2006 at 01:17:33PM -0500, Michiel De Hoon wrote: >For one of my software projects, I need the _kbhit function to check the >console for keyboard input. While this function is present in msvcrt.dll, it >is missing from cygwin1.dll, so I started writing this function my

Re: _kbhit & memory leak in select()

2006-02-05 Thread Corinna Vinschen
On Feb 5 13:17, Michiel De Hoon wrote: > 1) Where is the select_record deleted? The select_stuff variable sel will be > gone after we exit cygwin_select, and with it the pointer to the > select_record we allocated in select_read. In the select_stuff destructor. Corinna -- Corinna Vinschen

_kbhit & memory leak in select()

2006-02-05 Thread Michiel De Hoon
Hi everybody, For one of my software projects, I need the _kbhit function to check the console for keyboard input. While this function is present in msvcrt.dll, it is missing from cygwin1.dll, so I started writing this function myself (I'm hoping to contribute it to Cygwin if it works