From: Pete Batard <pbatard@gmail.com>
To: cygwin@cygwin.com
Subject: Re: w32api/include/winbase.h rev. 1.101, OVERLAPPED and -std=c99
Date: Thu, 03 Mar 2011 17:55:00 -0000 [thread overview]
Message-ID: <4D6FD581.2020807@gmail.com> (raw)
In-Reply-To: <20110303173737.GA16585@ednor.casa.cgf.cx>
On 2011.03.03 17:37, Christopher Faylor wrote:
> It's the other way around. Cygwin's winbase.h comes from MinGW. If
> there is an issue you need to take it up with the MingW folks.
Ah OK - will do then.
> OTOH, for Cygwin programs you shouldn't be using winbase.h at all.
For pure cygwin yes, but we wanted a common abstracted polling for
asynchronous transfers on Windows platforms, since poll() it's not
available in MSVC, and the only option then is to use an OVERLAPPED.
Anyway, thanks for the reply.
Regards,
/Pete
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2011-03-03 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 16:45 Pete Batard
2011-03-03 17:37 ` Christopher Faylor
2011-03-03 17:55 ` Pete Batard [this message]
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=4D6FD581.2020807@gmail.com \
--to=pbatard@gmail.com \
--cc=cygwin@cygwin.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).