public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Dave Korn <dave.korn@artimi.com>
Cc: cygwin@cygwin.com
Subject: RE: _kbhit
Date: Tue, 14 Feb 2006 04:00:00 -0000	[thread overview]
Message-ID: <1139888198.8591.411.camel@rosella.wigram> (raw)
In-Reply-To: <010301c630c8$fb06ff10$a501a8c0@CAM.ARTIMI.COM>

On Mon, 2006-02-13 at 18:11 +0000, 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 arises naturally in a dynamically 
linked application, where for one reason or another you end up 
mixing and matching plugins. After all, cygwin1.dll is just a 
Windows dll.

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


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

  reply	other threads:[~2006-02-14  3:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 17:18 _kbhit Michiel De Hoon
2006-02-13 18:12 ` _kbhit Christopher Faylor
2006-02-13 18:50 ` _kbhit Dave Korn
2006-02-14  4:00   ` skaller [this message]
     [not found] <6CA15ADD82E5724F88CB53D50E61C9AE9ECE5E@cgcmail.cgc.cpmc.co  lumbia.edu>
2006-02-16  1:48 ` _kbhit Arend-Jan Westhoff
2006-02-16  7:17   ` _kbhit Gary R. Van Sickle
2006-02-17 20:49     ` _kbhit Shankar Unni
2006-02-17 20:51       ` _kbhit Christopher Faylor
2006-02-18 21:30       ` _kbhit Gary R. Van Sickle
  -- strict thread matches above, loose matches on Subject: below --
2006-02-11  0:19 _kbhit Michiel De Hoon
2006-02-11  5:11 ` _kbhit Gary R. Van Sickle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1139888198.8591.411.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=cygwin@cygwin.com \
    --cc=dave.korn@artimi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).