From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Danny Smith <danny_r_smith_2001@yahoo.co.nz>
Cc: gdb@sources.redhat.com, mingw-users@lists.sourceforge
Subject: Re: [Mingw-users] Re: _WIN32?
Date: Thu, 03 May 2001 15:24:00 -0000
Message-id: <3AF1DAA0.3060702@cygnus.com>
References: <20010503211502.21716.qmail@web6401.mail.yahoo.com>
X-SW-Source: 2001-05/msg00056.html

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