Thread: A nested if inside the switch

Originally Posted by Syked4

Extro
Just a couple of observations:

You have declared 'pay' as an int and then go on to use it as a char

That's the correct way to do it, since getchar actually returns an integer. Read the FAQ as to why you have to use an int to test for EOF when using characters.

Originally Posted by Syked4

Second; the '\n' left in the buffer is causing the second prompt for input. There is a '\n' left in the buffer after the last call for input which is being immediately assigned to 'pay' in your while statement second time through satisfying the '\n' case.

:reads his last post: Yep, that's already been covered quite clearly.

Originally Posted by Syked4

While I know that it’s frowned on, using fflush(stdin) as the last line of your 'while' loop should take care of this.

No it shouldn't. There's nothing at all in the standard that says this should ever work. In fact, it should never work. The only reason it "works" ever is because Microsoft decided to ........ up^H^H^H^H^H^H^Hextend the language and make the function do something it should never do. fflush is used for output streams only. :reads his last post: Wait a minute, I already covered that too.

Originally Posted by Syked4

Thirdly getchar() only reads in one character, so using '-1' or 'EOF' to end your program wont work.getchar() will only load the '-' or the 'E'.

:reads last post again: Holy Deja Vu, Batman! I covered this too!

Originally Posted by Syked4

Maybe scanf is a better choice.

I wouldn't go that far. Wait a second! I already showed a better way to do this too!

Originally Posted by Syked4

EDIT: Missed your last post, so this refers to the code from post befor the do while change.

Apparently you missed my last post too, because I showed a better way to do everything you mentioned.


Quzah.

1) BUFSIZ is a macro defined in stdio.h. It is defined by the C standard.

2) The * denotes that you're using a pointer. A pointer is a variable that stores the address (memory location) of another variable. In this case:

Code:

char *promptAndAnswer ( char *buff, size_t size ) {

promptAndAnswer returns a pointer to a character. (Read it from right to left to easier understand it:

Code:

promptAndAnswer   /* the function... */
* /* returns a pointer to... */
char /* a character... */

)
Also, it as an argument takes a pointer to a character:

Code:

promptAndAnswer ( char *buff,

buff is a * pointer to a char

3) size_t is a data type defined by the C standard. It is defined to be an unsigned integeral type. Usually defined as an unsigned long, but it doesn't have to be. It only has to be unsigned, integeral. It's guarinteed to be safe for indexing arrays, as you can't run off the lower boundry. (Nothing stops you from running off the top end though, except your careful attention.)


Quzah.

quzah
Thanks for the slap and the fflushstdin() function. Both appreciated. In main should c be choice?

OPPS Two pages now. Thanks also for the explanations.

If your teacher thinks fflush(stdin) is a good idea, ask them what they think of gets().
If they don't recognise it's faults, then you're not going to learn anything useful from them, because they do not know enough C themselves.