weird bug in the scanf command

Code:

---

char array1[50];
scanf("%s", array1);

  printf("\nYou entered: %s\n", array1);

---

when i enter
"hello world"

it puts only the word "hello" in array1

It's not a bug. scanf() by definition is only going to read up until the first space or new line.

Check this code snippet out to see.

Code:

---

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

int main(int argc, char * argv[])
{
        char string1[20], string2[20];
        scanf("%s %s", string1, string2);
       
        printf("%s %s", string1, string2);
       
        return 0;
}

---

Since that's what it's supposed to do, the word "bug" seems a bit over-the-top.

what happens to the next word "world"

is it eliminated or it added to the start of the next input string?

Something like that, yes.

You are wanting to do something like this:

Example:

Code:

---

char line[256];
fgets(line, sizeof(line), stdin);
strtok(line, "\n");
printf("You typed: \"%s\"", line);

---

Quote:

---

Originally Posted by transgalactic2

what happens to the next word "world"

is it eliminated or it added to the start of the next input string?

---

It's held internally by the system in a keyboard buffer (aka the STDIN buffer for all intensive purposes) for your next scanf() or other read function.

puts reads all the inputted string

puts doesn't read anything. If you mean fgets, then yes.

i meant gets
sorry

gets reads every thing?

fgets, yes.
gets is an entirely different function, which is dangerous and bad.

how its bad?

http://cpwiki.sourceforge.net/Gets

gets doesnt know the size of the inputed string so it ma cause bufferoverflow

Yes, it may. And buffer overflows are bad.