Age | Commit message (Collapse) | Author |
|
|
|
|
|
No need for the complexity: the important distinction is between
"eof after reading something" and "eof right away". 0 is a natural
fit for eof after some data, and 1 is a natural fit for immediate eof.
Anything else can be scripted around this.
|
|
|
|
|
|
Oh hey, gcc 10.2 actually came with a useful new warning that
helps catch off-by-ones!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also make wait posix-compliant and update doc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
on, you guessed it, the BSDs!
|
|
|
|
everything is going to be okay, now now, please don't cry
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This pass makes variable size_t-ready, so everything works when
the prototypes are fixed in skalibs.
Some code uses "unsigned int *" where it should be "size_t *";
it cannot be changed now, but it's been marked with XXX. It must
change at the same time as the skalibs API.
|
|
|