This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug manual/6885] unclear descriptions of __fwriting and __freading


https://sourceware.org/bugzilla/show_bug.cgi?id=6885

paxdiablo <allachan at au1 dot ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |allachan at au1 dot ibm.com

--- Comment #1 from paxdiablo <allachan at au1 dot ibm.com> ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]