Re: fseek and open_memstream

In article <1170263751.020700.309560@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
<mark_bluemel@xxxxxxxxx> wrote:

Seeking back to the beginning is presumably regarded as preparation to
write again, so in effect it clears the buffer.

Or else fclose() causes a null to get written at the current position.

It's possible that you'll get an answer to this on some Linux newsgroup,
but the answer may be "oh, we forgot to specify exactly what happens when
you use fseek() on these extension streams".

-- Richard
--
"Consideration shall be given to the need for as many as 32 characters
in some alphabets" - X3.4, 1963.
.

Relevant Pages

  • Re: fseek and open_memstream
    ... so in effect it clears the buffer. ... Or else fclose() causes a null to get written at the current position. ... Doh! ...
    (comp.lang.c)
  • Re: Semantics of file.close()
    ... > yet by the kernel). ... > exception would be called on the write, ... But the writes are buffered, and close causes the buffer to be ... file.close can throw an exception just like fclose, ...
    (comp.lang.python)
  • Re: How to print PCL-Files ?
    ... and run it or use blinkers swpruncmd to start the batch,. ... fopen, fread, fwriteand fclose(). ... fwrite (prn_handle, buffer, n) ...
    (comp.lang.clipper)
  • Re: Speed up File access/read
    ... little bit stuck with converting the read bytes to my ... fclose(fid); ... buffer to an uint8 array, ...
    (comp.soft-sys.matlab)
  • file download dialog coming twice
    ... Response.Clear'clears the current output content from the buffer ... but file download dialog comes twice if i select open at first time.. ... Prev by Date: ...
    (microsoft.public.dotnet.framework.aspnet)