On Mon, Jun 24, 2019 at 4:51 PM Jon Zeppieri <zeppi...@gmail.com> wrote: > > `lseek` docs say: > > > The lseek() function shall allow the file offset to be set beyond the end > > of the existing data in the file. If data is later written at this point, > > subsequent reads of data in the gap shall return bytes with the value 0 > > until data is actually written into the gap. >
And the Windows call `SetFilePosition` is similar: > It is not an error to set a file pointer to a position beyond the end of the > file. The size of the file does not increase until you call the SetEndOfFile, > WriteFile, or WriteFileEx function. A write operation increases the size of > the file to the file pointer position plus the size of the buffer written, > which results in the intervening bytes uninitialized. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAKfDxxzx%3DiL-JQkJBx_SC%2BF05kG%2BUMW%2Bn%2BNWfsaDorvHcCdzkw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
