When/why is it a bad idea to use the fscanf() function?

Question

In an answer there was an interesting statement: \"It\'s almost always a bad idea to use the fscanf() function as it can leave your file pointer in an

Answer 1

When fscanf() fails, due to an input failure or a matching failure, the file pointer (that is, the position in the file from which the next byte will be read) is left in a position other than where it would be had the fscanf() succeeded. This is typically undesirable in sequential file reads. Reading one line at a time results in the file input being predictable, while single line failures can be handled individually.