Basic C question about scanf

[fyleow]

..

 

[IHateMyJob2004]

I think you need to use a loop. I think the space act as a delimiter.

I also suggest google.

 

[Thyme]

Just scan in the entire line at a time.

 

[daniel49]

perhaps you could use 2 vaiables one for first name and one for last? calling scanf twice.


or maybe try using gets()

something like
#include <stdio.h>

char input[81];
main()
{
puts("enter some text, then press enter");
gets(input);
printf("you entered %s" , input);
}



/*try those been quite a while since i played with C*/

 

[talyn00]

read character by character, until you get to a carriage return or newline. with some sort of while loop.

 

[kamper]

Originally posted by: daniel49
perhaps you could use 2 vaiables one for first name and one for last? calling scanf twice.


or maybe try using gets()

something like
#include <stdio.h>

char input[81];
main()
{
puts("enter some text, then press enter");
gets(input);
printf("you entered %s" , input);
}



/*try those been quite a while since i played with C*/

Ewww. Please don't advocate the writing of such code. gets is a hideously unsafe call to be making.

To the op, scanf is nasty for the same reason (dead simple buffer overflow). Since you're just reading a string anyways, may I suggest fgets?

 

[AllGoodNamesAreTaken]

Use the %[] format. For example ( not tested ):

char szFullName[ 32 ] = { '\0' };
scanf( "%31[a-zA-Z ]", szFullName );

 

[statik213]

Originally posted by: kamper

Ewww. Please don't advocate the writing of such code. gets is a hideously unsafe call to be making.

To the op, scanf is nasty for the same reason (dead simple buffer overflow). Since you're just reading a string anyways, may I suggest fgets?

isn't gets just a wrapper for fgets (using stdin as the stream)?

 

[kamper]

No, gets doesn't have a limit on buffer size. So if you pass in a pointer to a 50 byte piece of memory and the user enters 75, gets will write into unknown territory. fgets takes an int, limiting the number of characters it will get. Anything else is left on the stream for the next read. I suppose gets could call fgets with a number it knows is bigger than anything that could be on the stream, but it doesn't really matter.

The bottom line is that gets = bad.