Strange behavior if I use fgets() after fscanf()

Hi,

If i trying reading a line of text using an fgets() command after reading the previous line with fscanf(), fgets returns an empty line to me. And if I use another fgets() I get the line of text that I originally wanted to read. I have no issues if I just keep doing fgets one after the other..

Is there some issue with fscanf() that causes this.. or is it just my compiler doing something funny.? And any ideas on how to get around this?

thanks,

Avinash

Btw.. just in case its relevant, I am doing this on the Microsoft Visual C++ 2005 cl compiler. And for now, I got around it by reading the prev line with fgets and doing sscanf on it. But i would still like to know why this happens..

Avinash

The fscanf call leaves the newline in the input buffer. The fgets reads the newline and thinks it's an empty line.

so the approach I would recomend - do not mix fscanf with fgets - read all lines with fgets

and lines that need parsing - use sscanf on them

You should read this entire quite short thread now all the way thru.

Maybe start with post #2. It is about scanf functions and trapping the newline.

Hey,

Thanks a lot for the quick replies guys. It makes sense now.. Both the methods work. 'using only fgets and sscanf on what I need to parse' and also 'Just adding a space at the end of the fscanf statement so that it reads in the newline too". Appreciate your help..

Avinash