Skip in standard input/output stream

Asked Mar 28 '18 at 13:01

Active Mar 28 '18 at 13:22

Viewed 21 times

Why operations connected with changing pointer position in file needs to do one of those:

read value (i.e. fread())
flush stream (i.e. fseek())

For example: I know that next 10 bytes are unnecessary offset and I can simply skip them, so why I need to reset position indicator or read those 10 bytes and ignore them. I would want just move pointer those 10 bytes forward without any side effects. What is the reason behind it?

edited Mar 28 '18 at 13:10

asked Mar 28 '18 at 13:01

flush isn't done using `fseek` but `fflush` – Jean-François Fabre Mar 28 '18 at 13:03
to skip bytes from standard input, you need to read them & discard them. Seeking doesn't work, input streams (and output streams) aren't seekable. – Jean-François Fabre Mar 28 '18 at 13:04
But isn't that fseek needs to flush its cache before changing position? – Mar 28 '18 at 13:04
Maybe I misinterpreted something, I meant this one http://www.cplusplus.com/reference/cstdio/fseek/ – Mar 28 '18 at 13:06
Maybe I didn't understand clearly, but after reading that you wrote I assume that file is something like special case of stream that allows to do `fseek`? – Mar 28 '18 at 13:08
@Jean-FrançoisFabre `fseek()` does imply an `fflush()`. See https://stackoverflow.com/questions/7495891/will-fseek-function-flush-data-in-the-buffer-in-c – Andrew Henle Mar 28 '18 at 13:20
I must have misintepreted the first version of the question. I thought it was about stdin/stdout. – Jean-François Fabre Mar 28 '18 at 13:22
Could you please reopen this question? – Mar 28 '18 at 13:23
I have changed the duplicate target. This is still a duplicate. If I'm proven wrong, I'll reopen, no issue. – Jean-François Fabre Mar 28 '18 at 13:23

Skip in standard input/output stream

0 Answers0