The contents of the file are:
the code is:Code:dim 400 epsilon 0.001 ....
It doesn't seem to be working for the float number but works for the integer. What's wrong?Code:// read the dimension of the table fscanf(fp, "dim %d", &dimension); fprintf(stderr, "the dimension is %d\n", dimension); //printf("the dimension is %d\n", dimension); // read the fault tolerance (epsilon) fscanf(fp, "epsilon %f", &eps); fprintf(stderr, "epsilon is %f\n", eps);
fscanf returns a result, maybe check what that is?
TBH, use fgets() and sscanf for a more predictable outcome. If fscanf() errors out half-way through a line, you've got no idea where you are.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Thanks Salem. Breaking it up into pieces helped me to find the error.
The fscanf() was reading the new line character and not the next line.
The code which does the work is:
Code:fscanf(fp, "dim %d", &dimension); fprintf(stderr, "the dimension %d\n", dimension); getc(fp); fscanf(fp, "epsilon %lf", &eps); fprintf(stderr, "epsilon is %f\n", eps);
Again, it's better to just use fgets. Then you don't have to worry about crap stuck in the input buffer.
Originally Posted by Adak
I'll keep it in mind Elysia.
Isn't there any speed trade-off using these two statements instead of one?
You hardly need to worry about the performance.
If performance is low, then you would use a profiler to find the real bottleneck, which may or maybe not be what you think it is.
Don't worry about optimization prematurely.
