From: Mark Mitchell <mark@codesourcery.com>
To: Christopher Faylor <me@cgf.cx>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Windows sockets
Date: Sat, 26 Mar 2005 19:06:00 -0000 [thread overview]
Message-ID: <4245B29B.203@codesourcery.com> (raw)
In-Reply-To: <20050326174821.GA12793@trixie.casa.cgf.cx>
Christopher Faylor wrote:
> I guess you could only check for the existence of ws2_32 when the host
> is mingw, but that seems sort of redundant given that there is a
> preprocessor test which precisely tells what needs to be done.
Right.
> While
> I'm normally a big fan of using conditionals like "HAVE_WINSOCK", it
> doesn't seem like it makes the code any clearer to use these types of
> conditionals in this case unless we really anticipate that there will
> be another OS out there with some of the pecularities os Windows but
> not all of them.
>
> One observation is that maybe you could do something like:
>
> #if defined (__WIN32__) && !defined (__CYGWIN__)
> # define MINGW
> #endif
>
> and use #ifdef MINGW where appropriate.
If people would prefer that to WINAPI, that's fine by me.
(I'm not quite sure what we would call an environment in which the
compiler was Visual C, or some other non-GCC Windows compiler. Would
that still be MinGW? If not, then MINGW might not be as good a name,
which is why I went with WINAPI. But, I'm not concerned about how to
spell the conditional; whatever seems best to people is fine with me!)
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
next prev parent reply other threads:[~2005-03-26 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 1:27 Mark Mitchell
2005-03-26 2:09 ` Christopher Faylor
2005-03-26 8:47 ` Mark Kettenis
2005-03-26 17:38 ` Mark Mitchell
2005-03-26 17:48 ` Christopher Faylor
2005-03-26 19:06 ` Mark Mitchell [this message]
2005-03-26 21:03 ` Christopher Faylor
2005-03-26 22:00 ` Eli Zaretskii
2005-03-27 12:59 ` Kai Henningsen
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=4245B29B.203@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=me@cgf.cx \
/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