diff options
author | Michael Kerrisk <mtk.manpages@gmail.com> | 2019-05-09 09:43:55 +0200 |
---|---|---|
committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2019-05-09 09:43:55 +0200 |
commit | ebf20cddae622426cf525caa63918ac45f244809 (patch) | |
tree | b6d17e9a48ebc2c5c42c4ef89519924d31c018f4 | |
parent | 2e3023c413ec06dcb8d25cc48e8aab61f7da6b38 (diff) |
Changes: Expanded tabs
-rw-r--r-- | Changes | 24 |
1 files changed, 12 insertions, 12 deletions
@@ -142,18 +142,18 @@ tee.2 fopen.3 Elliot Hughes Explain BSD vs glibc "a+" difference - Where is the initial read position for an "a+" stream? - - POSIX leaves this unspecified. Most BSD man pages are silent, and - MacOS has the ambiguous "The stream is positioned at the end of - the file", not differentiating between reads and writes other than - to say that fseek(3) does not affect writes. glibc's documentation - explicitly specifies that the initial read position is the - beginning of the file. - - My new wording is based on the BSD implementations, so you may - prefer to replace the non-glibc section with "unspecified", or - indeed remove all claims about the initial read position. + Where is the initial read position for an "a+" stream? + + POSIX leaves this unspecified. Most BSD man pages are silent, and + MacOS has the ambiguous "The stream is positioned at the end of + the file", not differentiating between reads and writes other than + to say that fseek(3) does not affect writes. glibc's documentation + explicitly specifies that the initial read position is the + beginning of the file. + + My new wording is based on the BSD implementations, so you may + prefer to replace the non-glibc section with "unspecified", or + indeed remove all claims about the initial read position. mallinfo.3 Elliott Hughes |