getchar - multiple input problems

Hi,

I've run into a silly problem that I thought I'd ask for some help with:

Code:

---

#include <stdio.h>
#include <string.h>
#include <stdlib.h>

int i;//Global input var


//Example Menu
int main()
{
    printf("1) Save File \n");
    printf("2) Go Deeper \n");
    printf("3) Exit \n");
   
    userInput();
   
    while (i < 1 || i > 3)      //Errorcheck user input
    {
        printf("Wrong Input \n");
        main();
    }//end while

    switch (i)
    {
        case 1:
            //Save File
        break;

        case 2:
            //Go Deeper
        break;

        case 3:
            //Exit
        break;
}


//Getting Input
int userInput()
{
    getchar();                  //Fetch user input
   
    i = getchar();              //Assign user input
    i -= '0';                  //Convert to suitable int
}

---

The problem with the above example is that when I run it the "userInput();" validator ("Wrong Input") will trigger unless I manually linebreak or input a 'dummy character' infront of my wished menu input.

I know that this is caused because of the multiple (2) "getchar();" calls in "userInput();" however, my menu system has submenus running off the same functionality and if I were to Go deeper and eventually return to the main menu it would skip input unless I used the multiple (2) "getchar();" calls.

How would I go about solving this silly problem universally (inside "userInput();" )?

Any help would be greatly appriciated!
/Dregg

Ok first things first:

1) I fail to see how that even compiles, the switch is missing a bracket.

2) int main() should be int main(void) if you are not using command line arguments and should have return 0 at the end of main's body.

3) Don't use global variables. In a program of your size there is absolutely no need for them whatsoever. Use local variables and pass the correct arguments to functions that need parameters.

4) You don't need a new function just to read user input. In fact, I think that is part of the reason why you are confused about implementing your algorithm.

The idea is simple:

Print menu choices -> Read user input -> Print submenu choices -> read user input -> print menu choices, etc..

EDIT: Can't believe I didn't see this: DON'T EVER CALL MAIN() within main()!

Thanks for the reply!

Quote:

---

1) I fail to see how that even compiles, the switch is missing a bracket.

---

I realized that I forgot to mention that this is just a cut/paste from the actual program and it seems I accidently left one of the brackets out. Most of the functions are renamed just to make my question short and concise. (that goes for the faulty main(); call aswell)

Quote:

---

2) int main() should be int main(void) if you are not using command line arguments and should have return 0 at the end of main's body.

---

Thanks, forgot to add that.

Quote:

---

3) Don't use global variables. In a program of your size there is absolutely no need for them whatsoever. Use local variables and pass the correct arguments to functions that need parameters.

---

This is the start of a pretty extensive assignment that we are supposed to build on for the rest of the semester, so I'm trying to keep everything somewhat 'futureproof', besides wouldn't it be silly to define a local varaible for each submenu?

Quote:

---

4) You don't need a new function just to read user input. In fact, I think that is part of the reason why you are confused about implementing your algorithm.

---

What I was trying to achieve was a universal function for menu navigation to make the program easy to extend/update with new content, and also save a few lines of code. Maybe it is a bad idea? I just thought It would make it a bit simpler/cleaner, (since I would be reusing the same algorithm for each submenu anyway?)

Quote:

---

Originally Posted by Dregg

This is the start of a pretty extensive assignment that we are supposed to build on for the rest of the semester, so I'm trying to keep everything somewhat 'futureproof', besides wouldn't it be silly to define a local varaible for each submenu?

What I was trying to achieve was a universal function for menu navigation to make the program easy to extend/update with new content, and also save a few lines of code. Maybe it is a bad idea? I just thought It would make it a bit simpler/cleaner, (since I would be reusing the same algorithm for each submenu anyway?)

---

I think it is generally silly to use global variables when you don't need them. It is considered bad practice for a variety of reasons that I am not going to get into. In particular, while working in a larger project with many header and source files it can cause a lot of problems since you make it harder for yourself to identify which variable has local as opposed to global scope. It also makes it tempting to edit values of global variables in an attempt to debug existing problems in your code, forgetting that it may be used in more than one place and introducing even more false apparent problems. It really is like driving your groceries on the top of your car instead of in your trunk, they tend to stay fresher but by the time you get home you realize you are missing half of them.

I suspect that your problem is not with getchar() in particular since you can easily read documentation for that online. I don't know what the structure of your menu is, but if it is as recursive as you make it look, then it might be best to keep track of the depth you are at using some counter. If you want to print your menu based on your depth, then you can indeed have a menu function which takes as parameters the user input (which you read in main, or wherever) and the current depth and figures out what it needs to display as options.

Thanks for your reply, I'll take it all into consideration and try to correct this error, but somehow I still can't quite figure out whats missing, It's almost as if I need a separate algorithm for the main menu exclusivley.

To clarify:

The following works perfectly with the main menu as an exception (reads second char input):

Code:

---

int userIn()
{
    getchar();                  //Get user input
   
    i = getchar();              //Assign user input
    i -= '0';                  //Convert to suitable int
}

---

This one works as intended for the main menu but returns one faulty entry everytime I traverse between menus :

Code:

---

int userIn()
{ 
    i = getchar();              //Get & Assign user input
    i -= '0';                  //Convert to suitable int
}

---

Quote:

---

Originally Posted by Dregg

This is the start of a pretty extensive assignment that we are supposed to build on for the rest of the semester, so I'm trying to keep everything somewhat 'futureproof'

---

As the programs that you write get bigger, locality of reference becomes even more important: it is easier to understand a piece of code when you only have to consider a handful of variables involved than when you have to consider the hundreds of variables involved.

So it is with this piece of code:

Code:

---

userInput();

while (i < 1 || i > 3)      //Errorcheck user input

---

As I reader, I instantly go "huh? what's i?" Compare to this:

Code:

---

int input = userInput();

while (input < 1 || input > 3)

---

With the locality of reference and better naming, I don't even need the comment any more, yet a reader can easily understand that the input is being checked, and the reader can trace where the variable value is getting set. Now compare to this:

Code:

---

userInput();
foo();

while (i < 1 || i > 3)      //Errorcheck user input

---

userInput() sets the value of i to 0. Does the while loop run at all? You don't know, because you don't know if foo modified i.

Quote:

---

Originally Posted by Dregg

besides wouldn't it be silly to define a local varaible for each submenu?

---

Why would you need a local variable for each submenu?

Quote:

---

Originally Posted by Dregg

What I was trying to achieve was a universal function for menu navigation to make the program easy to extend/update with new content, and also save a few lines of code. Maybe it is a bad idea? I just thought It would make it a bit simpler/cleaner, (since I would be reusing the same algorithm for each submenu anyway?)

---

Then write a function that takes a menu text to display (and also the lower/upper limits of the range of input), requests for input, and returns the input if it is valid, otherwise it keeps getting the input.

Quote:

---

Originally Posted by laserlight

message

---

Thanks, laserlight for taking your time to answer! I'll revisit my code and keep legibility in mind!