Thread: Beginner Question -- From Absolute Beginner's Guide to C

To start, try changing your calls to scanf() from:

Code:

scanf("%.1f")

to

Code:

scanf("%f")

While scanf has provision for field width (i.e., you can limit the amount of characters taken in), it does not do precision (in other words, it is not analogous to printf() where you could specify how many digits after the decimal point are displayed). Your best bet might be to consult your local documentation for the scanf() function.

Google Search: man scanf

It would also be useful to check the return value from scanf() - it tells you how many values it succeeding in reading.

Also, if your book is guiding you to use fflush(stdin), burn it. fflush() has undefined behaviour for any input stream. It does not necessarily, contrary to what poor books or library documentation often say, discard pending input.

@ the OP: grumpy is right about the book you are using. Unfortunately it seems that there are multiple poor introductory C books published for every good one. One of the challenges of writing a tutorial type book is to quickly get the reader writing programs that work, in order to keep things interesting. After all, who wants to spend time writing and compiling programs that don't really do anything?

Yet one has to walk before they can run. The quickest (easiest?) way to get some input in C would be either the gets() function or (more often seen) the scanf() function. Yet these pose their own problems, and what often accompanies these functions in example code are hacky solutions to make them "work." As grumpy noted, fflush(stdin) is not a great way of doing things.

What is the best course of action then? As grumpy hinted, get a better book if possible. I would recommend The C Programming Language: Second Edition. It's a bit old now - it covers C89 standard C - yet there is still much there that is helpful. If you were to get that book, I would recommend reading Steve Summit's Notes to Accompany The C Programming Language, by Kernighan and Ritchie (``K&R'') along with it. Steve Summit is the maintainer of the comp.lang.c C-FAQ.

And speaking of FAQs, you should familiarize yourself with these three (in order):

1. comp.lang.c C-FAQ
2. cprogramming.com C and C++ FAQ
3. CPWiki FAQ

Being familiar with these will help you to recognize bad code practice. For example, all three answer questions about using fflush(stdin):

comp.lang.c FAQ:

• 12.26a How can I flush pending input so that a user's typeahead isn't read at the next prompt? Will fflush(stdin) work?
• 12.26b If fflush won't work, what can I use to flush input?

cprogramming.com FAQ:

• Why fflush(stdin) is wrong
• How do I flush the input buffer?

CPWiki FAQ:

• Why fflush(stdin) is bad.

There is a lot of reading there - perhaps it is overwhelming - but don't be discouraged. Remember you have to walk before you can run, but don't stop at walking.