Conrad T. Pino wrote:
The timer code in lib/nanosleep.c looks very good but I'm uncomfortable
making a commitment to making the change because:
* I don't understand UNIX style signal behavior well.
Basically, signals normally cause a process to exit unless a handler is
installed.
*
Conrad T. Pino wrote:
My ideas for the API are UNIX/POSIX specifications are non-negotiable and
internal APIs below that are discardable upon discovery of the better way.
Basically.
In theory, you could take up desired changes with the POSIX spec with
IEEE. Of course, if you did get some
Conrad T. Pino wrote:
Hi Derek,
From: Derek Price
I think renaming this file sys_types.h, starting it with `#include
sys/types.h', then defining what else you need would be an easier
interface to maintain.
Are you implying changing all #include sys/types.h in CVS? I assume no.
Paul Eggert wrote:
Derek Price [EMAIL PROTECTED] writes:
1. Corrects an incorrect check for a successful return from
getlogin_r to assume only 0 means success, per the POSIX2 spec:
http://www.opengroup.org/onlinepubs/009695399/functions/getlogin_r.html.
2. Moves the check
Hi,
Please test for the existence of:
directory: windows-NT/sys
new file: windows-NT/sys/types.h
I hope this is an update oversight that:
cvs update -dP windows-NT
will correct.
If none of the above is true then please send me
Microsoft's sys/types.h file from your
Derek Price wrote:
On the other hand, it would be nice if there were a way to specify a
default compression level or range of levels (both for the server and
the client) that could be used in the absence of any explicit
specification by the user. Of course, reconciling conflicting defaults
