mirrors/musl
1
0
Fork 0
mirror of https://git.musl-libc.org/git/musl synced 2025-02-16 02:04:10 +03:00
Code Issues Packages Projects Releases Wiki Activity

change stdio_ext __freading/__fwriting semantics slightly

Browse Source 
the old behavior was to only consider a stream to be "reading" or
"writing" if it had buffered, unread/unwritten data. this reportedly
differs from the traditional behavior of these functions, which is
essentially to return true as much as possible without creating the
possibility that both __freading and __fwriting could return true.

gnulib expects __fwriting to return true as soon as a file is opened
write-only, and possibly expects other cases that depend on the
traditional behavior. and since these functions exist mostly for
gnulib (does anything else use them??), they should match the expected
behavior to avoid even more ugly hacks and workarounds...
This commit is contained in:
Rich Felker 2012-06-17 21:24:58 -04:00
parent 3b43d10faf
commit deb90c79e5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/stdio/ext.c
View File

@ -14,12 +14,12 @@ int __fsetlocking(FILE *f, int type)
int __fwriting(FILE *f)
{
return f->wend && f->wpos > f->wbase;
return (f->flags & F_NORD) || f->wend;
}
int __freading(FILE *f)
{
return f->rend > f->rpos;
return (f->flags & F_NOWR) || f->rend;
}
int __freadable(FILE *f)