[Bug 215848] New: fopen(3): Incorrect good practice suggestion

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=215848

            Bug ID: 215848
           Summary: fopen(3): Incorrect good practice suggestion
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages@kernel-bugs.osdl.org
          Reporter: rootkea@gmail.com
        Regression: No

Hello!

From fopen(3):
"Therefore it is good practice (and indeed sometimes necessary under Linux) to
put an fseek(3) or fgetpos(3) operation between write and read operations on
such a stream."

I am not sure about the origin of this good practice but fgetpos(3) seems
wrong. It has to be fsetpos(3) if I'm reading the C standard and POSIX[0]
correctly.

BTW, calling fsetpos(3) will require a call to fgetpos(3) first. So why is it
being advised as a good practice to call two functions (`fgetpos` and then
`fsetpos`)? Maybe just i) mention fseek(3) only OR ii) mention fseek(3) and
fflush(3) (instead of fsetpos(3))?

[0]
https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/functions/fopen.html

Thanks!

Regards,
Avinash Sonawane (rootKea)
https://www.rootkea.me

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.