Summary: | unclear descriptions of __fwriting and __freading | ||
---|---|---|---|
Product: | glibc | Reporter: | Siward de Groot <siward> |
Component: | manual | Assignee: | Roland McGrath <roland> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | CC: | fweimer, glibc-bugs, lynneandallan |
Priority: | P2 | Flags: | fweimer:
security-
|
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
Siward de Groot
2008-09-13 18:29:05 UTC
Not sure what the confusion is there? Perhaps you could clarify. My reading is that, if you last wrote to a read/write (RW) file or if you've opened it write-only (whether you've written to it or not), you get back a true (non-zero) value. All other cases give you false (0), including a RW file where you've neither read nor written yet. Some may prefer to consider that a SchrodingerCat mode but the doco makes it quite clear here that __fwriting() returns false in that case. I agree that the quoted wording is clear enough, so closing. |