This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [Mingw-users] Re: _WIN32?
- To: Danny Smith <danny_r_smith_2001 at yahoo dot co dot nz>
- Subject: Re: [Mingw-users] Re: _WIN32?
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Thu, 03 May 2001 18:24:32 -0400
- Cc: gdb at sources dot redhat dot com, mingw-users at lists dot sourceforge
- References: <20010503211502.21716.qmail@web6401.mail.yahoo.com>
For:
> #ifndef _WIN32
> kill (PIDGET (inferior_pid), SIGINT);
> #endif
>
> would be replaced with something like this:
>
> #ifndef _N0_KILL_
> kill (PIDGET (inferior_pid), SIGINT);
> #endif
I'm actually puzzled. It looks very like someone took a shortcut and,
instead of implementing new methods, just went through and commented out
every call to kill(). cf handle_sigio().
Anyway, to answer your question:
> You are proposing that something like this in inflow.c
Yes, for the most part I would like to strongly encouraging people doing
WIN32, GO32 and CYGWIN ports to look back over all those #ifdef's and
see if they are better served by an autoconf feature test. Per my
earlier e-mail, the obvious oneis to do with how file systems are DOS
file systems are handled and there, I think things are being replaced
with a runtime test.
There is also at least one specific case, main.c, where I think the
_WIN32 test is bogus.
enjoy,
Andrew