path: root/src/stdio/ext.c
AgeCommit message (Collapse)AuthorLines
2012-06-17change stdio_ext __freading/__fwriting semantics slightlyRich Felker-2/+2
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...
2011-06-30fix logic in __fwritingRich Felker-1/+1
2011-06-30add and consolidate nasty stdio_ext junkRich Felker-0/+57
hopefully this resolves the rest of the issues with hideously nonportable hacks in programs that use gnulib.