> 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
> >
On Fri, Feb 17, 2006 at 12:27:52PM -0800, Shankar Unni wrote:
>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 spa
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
>
> I cannot confirm your assertion that msvcrt.dll and
> cygwin1.dll cannot be used together. If I compile the
> attached (almost C) file that dynamically links to msvcrt.dll
> using Cygwin:
> gcc -o kbhit.exe kbhit.cpp
> it compiles, links and works (on CMD and bash on CMD but not
> on
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,
>it
>> >is missing from cy
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
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
>> cmd.exe, in which case they're not a "
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 t
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 Windo
> 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
> 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 myself
(I
> 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
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 myself (I'm
>hopi
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
14 matches
Mail list logo
