diff options
author | Rich Felker <dalias@aerifal.cx> | 2018-08-28 19:16:40 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2018-08-28 19:16:40 -0400 |
commit | f66022dda8d18e6732626c7806f6c4d32023d574 (patch) | |
tree | 8eefb9fe10f74c6e0e1406aceceaa636ca9c68cb /src/stdio/open_memstream.c | |
parent | b39b47bac8ee5505cfc595000a140c35460e1cac (diff) | |
download | musl-f66022dda8d18e6732626c7806f6c4d32023d574.tar.gz musl-f66022dda8d18e6732626c7806f6c4d32023d574.tar.xz musl-f66022dda8d18e6732626c7806f6c4d32023d574.zip |
make fmemopen's w+ mode truncate the buffer
the w+ mode is specified to "truncate the buffer contents". like most of fmemopen, exactly what this means is underspecified. mode w and w+ of course implicitly 'truncate' the buffer if a write from the initial position is flushed, so in order for this part of the text about w+ not to be spurious, it should be interpreted as requiring something else, and the obvious reasonable interpretation is that the truncation is immediately visible if you attempt to read from the stream or the buffer before writing/flushing. this interpretation agrees with reported conformance test failures.
Diffstat (limited to 'src/stdio/open_memstream.c')
0 files changed, 0 insertions, 0 deletions