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

[bugzilla-daemon@kernel.org]

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

Alejandro Colomar (man-pages) (alx.manpages@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |alx.manpages@gmail.com
         Resolution|---                         |CODE_FIX

--- Comment #2 from Alejandro Colomar (man-pages) (alx.manpages@gmail.com) ---
Hi Avinash,

I decided to keep fsetpos(3) to not lose the info, so I applied the following
patch:


    fopen.3: tfix

    Reported-by: Avinash Sonawane <rootkea@gmail.com>
    Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>

diff --git a/man3/fopen.3 b/man3/fopen.3
index b9bbc4704..465031167 100644
--- a/man3/fopen.3
+++ b/man3/fopen.3
@@ -114,7 +114,7 @@ Therefore it is good practice (and indeed sometimes
necessary
 under Linux) to put an
 .BR fseek (3)
 or
-.BR fgetpos (3)
+.BR fsetpos (3)
 operation between write and read operations on such a stream.
 This operation may be an apparent no-op
 (as in \fIfseek(..., 0L, SEEK_CUR)\fP

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

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