Thread: Having 3 codes into 1

Hi everyone. I'm new to coding, just learning C.

I have three seperate codes I want to use and put together as one code:
1st:

Code:

{
    char firstName[255];
    char lastName[255];
        
    printf("Enter your First Name: ");
    scanf("%s", firstName);
    printf("Enter your Last Name: ");
    scanf("%s", lastName);
    printf("Hello, %s %s!\n", firstName, lastName);
    
}

2nd:

Code:

{
    char favColor[20];
    printf("Hello, firstname, What is your favorite color? ");
    gets(favColor);
    printf("\nThanks, Buddy! Now I know that your favorite color is %s\n", favColor);
    printf("\n");
}

3rd:

Code:

{
    bool stayAlive = true;
    char* userPrompt = "Do you want to exit this program (Y/N)? ";
    char c;
    printf("%s", userPrompt);
    while(stayAlive)
    {
        c = getchar();
        if(c == '\n')
            continue;
        else if(c == 'Y' || c == 'y')
            stayAlive = false;
        else
            printf("%s", userPrompt);
    }
    puts("\n\nHave a nice day, Buddy!");
    return 0;
    
}

I want to have all of these into one code for this program to work. The basics on what I want is:
- Person enters their name (Code 1)
- Gives a Greeting (Code 1)
- Welcomes the persons name, and asks their fav. color. (Code 2)
- Program tells them their fav. color. (Code 2)
- After those are done, program asks if person wants to leave. (Code 3)
All in that order. I was wondering if someone could help put this all together.
It all words excepte code 2. It prints the code, but doesnt allow the user to enter any info.

Thanks!

When you use scanf(), you leave the newline char behind in the input stream. So in #2, the gets() reads the input stream UP TO THE FIRST NEWLINE IT FINDS, and says "I'm done!", and the code goes on to the next line of code.

Add a getchar() after the scanf(), and see if that doesn't help out the gets() in #2. (This is a very frequent problem with students learning C, because neither the input stream, nor the newline, can be seen.)

Originally Posted by Adak

When you use scanf(), you leave the newline char behind in the input stream. So in #2, the gets() reads the input stream UP TO THE FIRST NEWLINE IT FINDS, and says "I'm done!", and the code goes on to the next line of code.

Add a getchar() after the scanf(), and see if that doesn't help out the gets() in #2. (This is a very frequent problem with students learning C, because neither the input stream, nor the newline, can be seen.)

Ok, I'm not understanding what you are saying....
could you provide an example?

@jacob ...

Have you tried just pasting the 3 sections into one .c file and compiling it?

From there its mostly a matter of eliminating errors and debugging your code.

Yes, I did try. But still didnt work.

Originally Posted by JacobC

Ok, I'm not understanding what you are saying....
could you provide an example?

Sure. print any value that you have entered via scanf(). Does the cursor stay on the same row of text as it started with?

Yes, it does. That means that the object you entered does NOT contain a newline char - but clearly you DID hit the enter key! So where is the newline that was generated when you pressed the enter key?

Hiding in the Amazon jungle?

Nope! It's waiting in your keyboard buffer - for your very NEXT input - to POUNCE on it. It's no problem for numbers, because they're larger, and scanf() for them, will scan over them -- too small they are. But for a char? They're perfectly sized. For a fgets() that always ends it's input by checking for a newline - perfect!

Originally Posted by Adak

Sure. print any value that you have entered via scanf(). Does the cursor stay on the same row of text as it started with?

Yes, it does. That means that the object you entered does NOT contain a newline char - but clearly you DID hit the enter key! So where is the newline that was generated when you pressed the enter key?

Hiding in the Amazon jungle?

Nope! It's waiting in your keyboard buffer - for your very NEXT input - to POUNCE on it. It's no problem for numbers, because they're larger, and scanf() for them, will scan over them -- too small they are. But for a char? They're perfectly sized. For a fgets() that always ends it's input by checking for a newline - perfect!

Ok, when I execuite the command, this is what I get,
http://i1198.photobucket.com/albums/...re524/hihi.jpg
It skips the second code...
could you rewrite it so I can see what I did wrong?

Originally Posted by Adak

Hiding in the Amazon jungle?

That would explain the outcry about this constantly accumulating pile of bits of trash down there....

Originally Posted by JacobC

Ok, when I execuite the command, this is what I get,
http://i1198.photobucket.com/albums/...re524/hihi.jpg
It skips the second code...
could you rewrite it so I can see what I did wrong?

Yes it does... and Adak just told you why.
You need to listen to him.

Originally Posted by CommonTater

Yes it does... and Adak just told you why.
You need to listen to him.

like I said, I have no ........ing clue on what to do in C.
Im totally new, and know nothing.

Originally Posted by JacobC

like I said, I have no ........ing clue on what to do in C.
Im totally new, and know nothing.

Then you don't need to be coming in here swearing and whining.

Grab yourself a decent book or tutorial... start on page 1, read the whole thing, every word, do all the examples and exercises... by the time you get to the last page I should hope you will realize just how ridiculous you sound.