Tests: Stream: Use a quote from C99 spec

Use C99 instead of Linux man entry.
pull/9033/head
Filip Jagodzinski 2018-12-10 16:30:16 +01:00
parent 89a475bc4e
commit 91e9010dd2
1 changed files with 8 additions and 10 deletions

View File

@ -23,17 +23,15 @@
/* This test suite verifies that write/read/write/read sequence can be /* This test suite verifies that write/read/write/read sequence can be
* successfully executed on the Stream objects. * successfully executed on the Stream objects.
* *
* A qute from `man 3 fdopen`: * A qute from C99 standard, paragraph 7.19.5.3, point 6:
* *
* Reads and writes may be intermixed on read/write streams in any order. Note * When a file is opened with update mode ('+' as the second or third character in the
* that ANSI C requires that a file positioning function intervene between * above list of mode argument values), both input and output may be performed on the
* output and input, unless an input operation encounters end-of-file. (If * associated stream. However, output shall not be directly followed by input without an
* this condition is not met, then a read is allowed to return the result * intervening call to the fflush function or to a file positioning function (fseek,
* of writes other than the most recent.) Therefore it is good practice (and * fsetpos, or rewind), and input shall not be directly followed by output without an
* indeed sometimes necessary under Linux) to put an fseek(3) or fgetpos(3) * intervening call to a file positioning function, unless the input operation encounters end-
* operation between write and read operations on such a stream. This operation * of-file.
* may be an apparent no-op (as in fseek(..., 0L, SEEK_CUR) called for its
* synchronizing side effect).
*/ */
using utest::v1::Case; using utest::v1::Case;