From: kaih@khms.westfalen.de (Kai Henningsen)
To: gdb-patches@sources.redhat.com
Subject: Re: Follow-up on patch to ser-tcp.c
Date: Thu, 07 Apr 2005 07:20:00 -0000 [thread overview]
Message-ID: <9UPPQfJ1w-B@khms.westfalen.de> (raw)
In-Reply-To: <200504060739.j367dlM3000821@elgar.sibelius.xs4all.nl>
mark.kettenis@xs4all.nl (Mark Kettenis) wrote on 06.04.05 in <200504060739.j367dlM3000821@elgar.sibelius.xs4all.nl>:
> Actually I think the WINAPI thingy is more descriptive. In light of
> the discussion above, I think there should be a single spot in
> configure.ac where we decide whether we want to use the native Windows
> API or the proper POSIX interfaces that Cygwin provides get used.
> Some sort of "Windows but not Cygwin" would than add -lws2_23 and
> define something like USE_WIN32API, and we'd use that define
> everywhere where there is a choice between the native Windows API and
> the proper POSIX interfaces.
I seem to recall that autoconf does know something about that difference.
> Great! In this area we also have the ioctlsock v.s. ioctl issue. Is
> it possible to keep using the proper POSIX interfaces in the code and
> #define ioctl ioctlsock in the USE_WIN32API case instead of the other
> way around? I think that makes it easier for non-Windows programmers
> to understand the code.
The whole point is that Windows has two different ioctl functions, whereas
POSIX only has one. Now if you never need to use the non-socket ioctl on
Windows, that would be possible - otherwise ...
MfG Kai
prev parent reply other threads:[~2005-04-07 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 18:07 Mark Mitchell
2005-04-06 7:41 ` Mark Kettenis
2005-04-06 17:52 ` Mark Mitchell
2005-04-07 7:20 ` Kai Henningsen [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=9UPPQfJ1w-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=gdb-patches@sources.redhat.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