From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: RFA: Support Windows extended error numbers in safe_strerror
Date: Sun, 05 Feb 2006 04:48:00 -0000 [thread overview]
Message-ID: <uwtga4diw.fsf@gnu.org> (raw)
In-Reply-To: <20060205002710.GC8728@trixie.casa.cgf.cx> (message from Christopher Faylor on Sat, 4 Feb 2006 19:27:10 -0500)
> Date: Sat, 4 Feb 2006 19:27:10 -0500
> From: Christopher Faylor <me@cgf.cx>
>
> >Then perhaps we should create a new -nat.c file, say mingw-nat.c, and
> >maintain it separately. (For that matter, I'd really love to see
> >win32-nat.c be renamed to cygwin-nat.c, since that's what it really is
> >going to be.) If neither Daniel nor Mark M. can afford becoming
> >responsible maintainers for such a new native file, I volunteer to do
> >my best to do that.
> >
> >Would you agree to such a solution?
>
> That is *exactly* what I expected to come out of this discussion. And,
> I suspect that it won't just be win32-nat.c which will have to be changed.
> There will be a header file or two, and probably some configuration magic.
Whatever it takes, yes.
> And, really, it is a bad design decision to have two different files
> using the same debugging mechanism. If this was to be done right then
> win32-nat.c should somehow be factored out further so that the common
> bits can be shared. Cygwin and MinGW are alike enough that they should
> share code.
That would be going back to where you don't want to: to a maintenance
burden on you, due to sharing code with MinGW.
> I think Ulrich's point was that wasting time tinkering with code to make
> it work better with non-POSIX platforms was counter-productive for
> projects which are designed to run on same.
I think Ulrich's point was that it would be waste of Ulrich's time to
do what Ulrich doesn't want to do.
next prev parent reply other threads:[~2006-02-05 4:48 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 21:55 Daniel Jacobowitz
2006-02-03 23:25 ` Mark Kettenis
2006-02-03 23:39 ` Christopher Faylor
2006-02-04 3:27 ` Daniel Jacobowitz
2006-02-04 6:29 ` Jim Blandy
2006-02-04 10:33 ` Eli Zaretskii
2006-02-04 10:59 ` Eli Zaretskii
2006-02-04 14:35 ` Mark Kettenis
2006-02-04 14:52 ` Daniel Jacobowitz
2006-02-04 15:14 ` Eli Zaretskii
2006-02-05 0:15 ` Christopher Faylor
2006-02-05 4:46 ` Eli Zaretskii
2006-02-05 19:34 ` Christopher Faylor
2006-02-05 19:49 ` Daniel Jacobowitz
2006-02-05 20:19 ` Eli Zaretskii
2006-02-05 20:22 ` Daniel Jacobowitz
2006-02-05 21:50 ` Christopher Faylor
2006-02-05 21:57 ` Daniel Jacobowitz
2006-02-05 22:33 ` Christopher Faylor
2006-02-05 22:41 ` Daniel Jacobowitz
2006-02-06 6:35 ` Christopher Faylor
2006-02-06 17:26 ` Daniel Jacobowitz
2006-02-05 22:59 ` Eli Zaretskii
2006-02-05 22:47 ` Eli Zaretskii
2006-02-06 2:41 ` Daniel Jacobowitz
2006-02-06 4:20 ` Eli Zaretskii
2006-02-05 22:57 ` Eli Zaretskii
2006-02-05 22:44 ` Christopher Faylor
2006-02-05 23:07 ` Eli Zaretskii
2006-02-06 5:14 ` Christopher Faylor
2006-02-06 7:20 ` Eli Zaretskii
2006-02-06 8:47 ` Corinna Vinschen
2006-02-06 12:07 ` Bob Rossi
2006-02-06 14:23 ` Daniel Jacobowitz
2006-02-06 18:37 ` Eli Zaretskii
2006-02-04 10:03 ` Eli Zaretskii
2006-02-05 0:27 ` Christopher Faylor
2006-02-05 2:01 ` Daniel Jacobowitz
2006-02-05 4:49 ` Eli Zaretskii
2006-02-05 7:39 ` Jim Blandy
2006-02-05 20:01 ` Eli Zaretskii
2006-02-05 20:20 ` Daniel Jacobowitz
2006-02-05 22:45 ` Eli Zaretskii
2006-02-06 2:38 ` Daniel Jacobowitz
2006-02-05 4:48 ` Eli Zaretskii [this message]
2006-02-04 1:06 ` Jim Blandy
2006-02-04 3:00 ` Daniel Jacobowitz
2006-02-04 6:22 ` Ian Lance Taylor
2006-02-04 10:29 ` Eli Zaretskii
2006-02-04 13:53 ` Mark Kettenis
2006-02-04 15:17 ` Eli Zaretskii
2006-02-04 10:24 ` Eli Zaretskii
2006-02-04 15:33 ` Mark Kettenis
2006-02-04 15:35 ` Eli Zaretskii
2006-02-04 10:20 ` Eli Zaretskii
2006-02-04 13:14 ` Mark Kettenis
2006-02-05 7:41 ` Jim Blandy
2006-03-02 0:53 ` Michael Snyder
2006-02-04 11:58 ` Eli Zaretskii
2006-02-04 14:53 ` Daniel Jacobowitz
2006-02-04 15:09 ` Eli Zaretskii
2006-02-04 15:57 ` David Ayers
2006-02-06 17:35 ` Daniel Jacobowitz
2006-02-06 17:54 ` Christopher Faylor
2006-02-06 18:23 ` Jim Blandy
2006-02-06 19:08 ` Eli Zaretskii
2006-02-06 19:58 ` Daniel Jacobowitz
2006-02-06 20:59 ` Daniel Jacobowitz
2006-02-06 22:55 ` Mark Kettenis
2006-02-06 22:58 ` Daniel Jacobowitz
2006-02-08 0:08 ` Daniel Jacobowitz
2006-02-08 21:08 ` Mark Kettenis
2006-02-08 21:12 ` Bob Rossi
2006-02-08 23:17 ` Mark Kettenis
2006-02-08 23:23 ` Daniel Jacobowitz
2006-02-09 0:12 ` Joel Brobecker
2006-02-09 1:54 ` Bob Rossi
2006-02-09 7:47 ` Eli Zaretskii
2006-02-09 9:18 ` Jim Blandy
2006-02-08 21:54 ` Eli Zaretskii
2006-02-08 23:10 ` Mark Kettenis
2006-02-08 23:22 ` Daniel Jacobowitz
2006-02-09 14:40 ` Mark Kettenis
2006-02-09 15:14 ` Daniel Jacobowitz
2006-02-09 20:24 ` Eli Zaretskii
2006-02-09 8:00 ` Eli Zaretskii
2006-02-09 14:44 ` Mark Kettenis
2006-02-09 14:57 ` Daniel Jacobowitz
2006-02-09 20:40 ` Eli Zaretskii
2006-02-09 21:06 ` Daniel Jacobowitz
2006-02-09 22:13 ` Eli Zaretskii
2006-02-09 20:26 ` Eli Zaretskii
2006-02-09 22:37 ` Daniel Jacobowitz
2006-02-10 7:53 ` Eli Zaretskii
2006-02-10 16:18 ` Christopher Faylor
2006-02-10 16:49 ` Daniel Jacobowitz
2006-02-10 18:18 ` Eli Zaretskii
2006-02-10 21:56 ` Daniel Jacobowitz
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=uwtga4diw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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