Hal Murray :
> What's the story with HAVE_IO_COMPLETION_PORT? Do we know what that is for?
Yes, though I could't have told you that yesterday.
An IO completion part is a place where a process doing asynchronous I/O can
look to see which such requests have completed, rather analogous to looking
a
> Good point. I think they can go.
OK. I'll remove them.
There is also SIGDANGER. I think that is something about running low on
memory on AIX.
What's the story with HAVE_IO_COMPLETION_PORT? Do we know what that is for?
--
These are my opinions. I hate spam.
___
make sure they are defined by the posix level we are targeting
On Mon, Sep 12, 2016, 4:01 PM Eric S. Raymond wrote:
> Hal Murray :
> >
> > Our current code has ifdefs for SIGQUIT and several others. That may
> have
> > been leftover from Windows.
> >
> > man 7 signal says:
> >First the
Hal Murray :
>
> Our current code has ifdefs for SIGQUIT and several others. That may have
> been leftover from Windows.
>
> man 7 signal says:
>First the signals described in the original POSIX.1-1990 standard.
>
>
> Can we remove those ifdefs? If not, what environment are we consid
Our current code has ifdefs for SIGQUIT and several others. That may have
been leftover from Windows.
man 7 signal says:
First the signals described in the original POSIX.1-1990 standard.
Can we remove those ifdefs? If not, what environment are we considering that
doesn't have them?
