From: Mark Mitchell <mark@codesourcery.com>
To: gdb-patches@sources.redhat.com
Cc: Mark Kettenis <kettenis@gnu.org>
Subject: Follow-up on patch to ser-tcp.c
Date: Tue, 05 Apr 2005 18:07:00 -0000 [thread overview]
Message-ID: <4252D364.7050304@codesourcery.com> (raw)
Mark --
A while back, I posted a patch to change ser-tcp.c to support Windows, here:
http://sources.redhat.com/ml/gdb-patches/2005-03/msg00331.html
You had some objections:
1. The configury change to link with -lws2_23 on Windows.
2. The use of #ifdef WINAPI.
3. The asymmetry I introduced by adding the "read_prim" member to
"struct serial" without a corresponding "write_prim" member.
4. Changes to support differences between BSD and Windows socket APIs.
5. Modifications to strerror.
I don't see a way around (1). The question is really not whether the
library is available; the question is whether we should use it. On
MinGW, we should; on Cygwin, we should not.
The impact of (2) can be mitigated by using __MINGW32__ instead of
WINAPI. That will avoid the defs.h change, and localize the changes to
the actual conditional code.
In my local version of the patch, I've corrected (3); the symmetry is
now complete. I've also mitigated (4), in that I've determined that
send/recv should work fine on all targets. That means that we don't
need an #ifdef to decide whether to use "read" or "recv"; we can just
always use "recv", as that function is available both on Windows and
elsewhere.
I can drop (5) from the patch, and we can come back to that later.
With the set of changes described here, would you be willing to consider
the patch again? If so, I will post the modified version.
Thanks,
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
next reply other threads:[~2005-04-05 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 18:07 Mark Mitchell [this message]
2005-04-06 7:41 ` Mark Kettenis
2005-04-06 17:52 ` Mark Mitchell
2005-04-07 7:20 ` 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=4252D364.7050304@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
/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