From: Christopher Faylor <me@cgf.cx>
To: Mark Mitchell <mark@codesourcery.com>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Windows sockets
Date: Sat, 26 Mar 2005 21:03:00 -0000 [thread overview]
Message-ID: <20050326210307.GA14720@trixie.casa.cgf.cx> (raw)
In-Reply-To: <4245B29B.203@codesourcery.com>
On Sat, Mar 26, 2005 at 11:06:03AM -0800, Mark Mitchell wrote:
>Christopher Faylor wrote:
>>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!)
Huh. I don't know. I didn't even consider that gdb would build with
Visual C.
Actually, for the last four or five years, Cygwin's gcc hasn't defined
__WIN32__, so just using __WIN32__ would probably be sufficient.
Otherwise, I guess you're right, WINAPI makes the most sense.
cgf
next prev parent reply other threads:[~2005-03-26 21:03 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
2005-03-26 21:03 ` Christopher Faylor [this message]
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=20050326210307.GA14720@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=gdb-patches@sources.redhat.com \
--cc=mark@codesourcery.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