Related
#include <stdio.h>
#include <stdlib.h>
int main() {
char a;
printf("What? \t");
scanf("%s", &a);
printf("U have to %s", a);
return 0;
}
Whenever I build and run this code and enter a value in %s, I get an error and the debug program stops working and closes. But when I use ampersand sign like this:
#include <stdio.h>
#include <stdlib.h>
int main() {
char a;
printf("What? \t");
scanf("%s", &a);
printf("U have to %s", &a);
return 0;
}
in the printf... it works. Why is that? It also differs between the format specifier, such as one doesn't need to put & (ampersand) sign in printf when one uses %c or %d in the scanf. Why does this happen and is it related to the data types and which format specifiers concludes this result?
(sorry for my bad English. I am not a native English speaker and this is my first time here).
What you have here is a classic example of code that seems to work, but for the wrong reasons.
Let's review a few things about printf and scanf. The format specifier %d is for values of type int. You can read an integer like this:
int i;
scanf("%d", &i);
And you can print it back out like this:
printf("%d\n", i);
Why does one use an & and one does not? Well, C uses what's called "pass by value". If we wrote
scanf("%d", i); /* WRONG */
we would be passing the value of i to scanf. But we don't want to pass the (old) value of i to scanf, we want scanf to read a new value, and store it into i. In other words, we want scanf to, in effect, pass the new value of i back to us. For that to work, we instead pass scanf a pointer to the variable i where we want it to store the just-read integer. That's what the & does -- it generates a pointer to i.
When we call printf, on the other hand, the regular way of passing arguments works just fine. We do want to pass i's value to printf so that it can print it out. If we were to call
printf("%d\n", &i); /* WRONG */
it wouldn't work, because printf expects an int, and here we're wrongly handing it a pointer-to-int.
So now we've learned that for integers with %d, printf wants an int and scanf wants a pointer-to-int.
Let's talk about characters. The format %c is for characters. We can read one character with scanf:
char c;
scanf("%c", &c);
And we can print it with printf:
printf("%c\n", c);
Again, the pattern is exactly the same. scanf needs a pointer, so that it can fill in the value, so we pass &c. But printf just needs the value, so we pass plain c.
Now we get to strings. A string in C is an array of characters. Also strings in C are always terminated by a special null character, '\0', that marks the end of the string. So if we wanted to declare a variable that could contain strings up to 9 characters long, we might write
char s[10];
That gives us room for 9 characters, plus the terminating '\0'.
But arrays are special in C: Whenever you pass an array to a function, or whenever you do anything that would require the "value" of the array, what you get instead (what the compiler automatically generates for you) is a pointer to the array's first element.
What this means is that to read a string with scanf and %s, we can just call:
scanf("%s", s);
"But where is the &?", you ask. "I thought you always needed an & when calling scanf!"
Well, not quite. You always need a pointer when calling scanf. And in fact, when you called scanf("%s", s), it was just as if you had written
scanf("%s", &s[0]);
When you use %s with scanf, it expects a pointer to the first of several characters, that is, a pointer to the beginning of an array of characters, where it should begin writing the string it reads. (How does it know how big the array is? What if the user types a string that's too long to fit in the array? We'll get to those points in a moment.)
You can print strings with %s too, of course, and it looks like this:
printf("%s\n", s);
This is, again, just as if you had written
printf("%s\n", &s[0]);
When you use %s with printf, it expects a pointer to the first of several characters which it should begin printing, until it finds the terminating '\0' character.
So %s is special with printf and scanf, because strings are special (because arrays are special). With %d and %c and just about every other format specifier, you usually need a & when you call scanf, and you usually don't want that & when you call printf. But with %s, you usually don't want the & for either printf or scanf.
(And if we think about it a bit more carefully, the exception is not so much that scanf and %s does not need the &. Remember, the rule is really, scanf always needs pointers. The only reason scanf and %s doesn't need an & is that when you pass an array, you get a pointer to the array's first element automatically. So the exception is really for printf and %s: printf and %s does expect a pointer, and the reason printf and %s is designed to expect a pointer is that there's no way to not give it one: it has to accept a pointer, because for strings, that's what you always end up giving it.)
So the rule with %s is that scanf expects a pointer to the first of several characters, and printf expects a pointer to the first of several characters, too.
So now, with all that background out of the way, we can look at your code. You basically wrote
char c;
scanf("%s", &c);
At first this might seem to be kinda, sorta, almost correct. scanf and %s wants a pointer to a character, and you gave it &c, which is a pointer to a character. But %s really wants a pointer to the first of several characters. But you gave it a pointer to just a single character. So when the user types a string, the first character typed will get stored in c, but the rest of the characters, and the terminating '\0', will get written to unallocated memory somewhere off to the right of variable c. They'll overwrite ("clobber") memory that was, perhaps, used for something else. This is a serious problem, but it might not become evident right away.
Finally, you tried to print things out again with printf. You first tried
printf("%s\n", c); /* WRONG */
but this didn't work at all. The reason is that %s with printf expects a pointer-to-char, but you gave it a plain char. Suppose c contains the letter 'A'. This would end up asking printf to go to address 65 and begin printing characters until it finds the terminating '\0'. Why address 65? Because 65 is the ASCII code for A. But there's probably not a proper, null-terminated string starting at address 65 in memory; in fact there's a good chance your program doesn't have permission to read from address 65 at all.
So then you tried
printf("%s\n", &c); /* ALSO WRONG */
and this seemed to work. It "worked" because, if scanf succeeded in storing a complete string into c and the unallocated memory off to the right of it, and if clobbering that memory somehow didn't cause (too many) other problems, then when you pass the pointer &c to printf, printf can find those characters, making up a string, and print them out.
So it "works", but as I said, for the wrong reasons: in the process it stomps all over memory it doesn't "own", and sooner or later, something else is going to not work as a result.
How should you have scanned and printed a string? One way is like this, as we saw before:
char s[10];
scanf("%s", s);
printf("%s\n", s);
Now when scanf gets a pointer to the first element of the array s, it has 10 characters to play with.
We really do have to worry about the possibility that the user will type more than 9 characters. But there's a fix for that: we can tell scanf how long a string it's allowed to read, how many characters it's allowed to write to the array we handed it:
scanf("%9s", s);
That 9 in there tells scanf that it's not allowed to read more than 9 characters from the user. And since 9 is less than 10, there's still room for the terminating '\0' character.
There's much more that could be said about scanf. As chqrlie noted in a comment, it's important to check its return value, to make sure it succeeded in converting as many values as you wanted it to. It's got some strange rules about whitespace. Unless you know what you're doing, you can't intermix calls to scanf with calls to other input-reading functions like getchar or fgets -- you'll get strange results. And, finally, scanf is so persnickety and (in the end) so lacking in truly useful functionality that it's not really worth using at all. But those are topics for another day, since this answer is tl;dr already.
The %s format specifier requires a pointer to a string. When used with scanf, it must be a char array with enough characters for the word you enter plus the trailing null byte that indicates the end of the string. In printf() it has to be a null-terminated char array.
Using a pointer to a char variable doesn't work, because it doesn't have room for the null byte. You're causing undefined behavior by writing outside the variable.
char word[100];
scanf("%s", word);
printf("%s\n", word);
You can use %c to read and write a single character rather than a string of multiple characters.
char letter;
scanf("%c", &letter);
printf("%c\n", letter);
In statement char a; a is a character variable & to scan a char variable use %c format specifier.
scanf("%s",a);/* %s expects base address of char buffer, not single char */
scanf(" %c",&a);/* this is correct */
If you want to scan using %s then your input should be char buffer like char buf[10]. for e.g
char a[10];
scanf("%s",a);
u don't need to put &(ampersand) sign in printf when u use %c or %d ? no need to provide address & to printf() as printf() job is to print not to scan. for e.g
char input;
scanf("%c",&input);/* here you need &, As scanf() will store input char into
address you provided i.e &input */
printf("%c",input);/*here no need &input, bcz input char already stored,
printf will just print the char*/
Well, if you print the address you can use %p.
printf("%p",a);/*a is char buffer */
I have the following code.
int ant = 10;
char converter = ant;
printf("This is where the char prints: %c", converter);
Why does the console only print out when this is run:
This is where the char prints:
Why does this happen? And is it possible to still use the %c and print out the value?
I understand that changing the %c to a %d will allow me to see the result but i wanna know why.
You are printing out the character encoded by the number 10: the format specifier %c is used to output the characters, rather than their numerical values.
In ASCII (most likely the encoding used), that's \n; the linefeed character. Your terminal is probably able to deal with that, and you'll see an extra line in your output.
If you want to print the numeric value of converter, then use simply %d as the format specifier (the char types are converted implicitly to int types at the calling site).
#include<stdio.h>
#include<string.h>
void main()
{
char a,b,c;
printf("Enter alien names:\n");
scanf("%s\n%s\n%s\n",a,b,c);
printf("The alien names are %s, %s and %s. A meteor hit %s's spaceship. A star scratched %s\'s spaceship. But %s fixed %s and %s\'s spaceships. The three became friends and are from the planet BYG (which means BLUE YELLOW GREEN)",a,b,c,a,b,c,a,b);
}
What is the specific reason for the runtime error I'm getting here?
To solve this issue you should simply consider to use strings (arrays of chars) to contain the different names.
Here is an example how to do that:
void main()
{
// The string "a" can contain up to 100 symbols (chars).
char a[100];
printf("Enter an alien name:\n");
scanf("%s",a);
printf("The alien name is %s.", a);
}
The difference between "char a" and "char a[100]" is that in the first case the variable "a" corresponds to a single character and in the second it corresponds to a string - an array of chars which can contain up to 100 characters.
The posted code has undefined behavior, because the variables a, b, and c are of type char, while the %s conversion specifier in the call to scanf() is expecting a pointer to the first element of a character array that can hold the input string. Mismatched conversion specifers and arguments in a scanf() call lead to undefined behavior, and attempting to write too many characters into the receiving array causes undefined behavior.
The first problem can be fixed by declaring a, b, and c as arrays large enough to hold expected input:
char a[100], b[100], c[100];
...
scanf("%s\n%s\n%s\n", a, b, c);
Note that arrays decay to pointers to their first elements in most expressions, including function calls, so here a is a pointer to the first element of the character array a[]; this is equivalent to &a[0].
There is still a possibility for undefined behavior if the user enters too many characters. To avoid this, always specify a maximum width when using scanf() to read user input into a string. Note here that the specified width is the maximum number of characters that will be read for that input item, not including the null terminator, \0, which will be automatically added by scanf(), so the maximum width must be at least one less than the size of the receiving array:
scanf("%99s\n%99s\n%99s\n", a, b, c);
But if you compile and run this code, you will find that it does not behave as expected. After the third name is entered, the program will continue waiting for more input. This is because the \n character is a whitespace character, and when scanf() encounters a whitespace character in a format string, it reads and discards zero or more whitespace characters in the input until a nonwhitespace character is encountered, or until no more characters can be read. The %s directive tells scanf() to read characters until a whitespace character is encountered. So when the user presses Enter after the final name, scanf() completes matching input characters for the final name and returns the \n character to the input stream; then the \n is reached in the above format string, and scanf() matches the aforementioned \n character in the input stream, and any further whitespace characters that are encountered. This will end if the user enters another nonwhitespace character, or signals end-of-file from the keyboard (e.g., with Ctrl-D or Ctrl-Z).
To avoid this complication, remember that it is almost never correct to end a scanf() format string with a whitespace character. Also, there is no need to use \n rather than a space character, since both are simply interpreted as whitespace directives by scanf():
scanf("%99s %99s %99s", a, b, c);
It would further improve the posted code if the return value from the call to scanf() were checked before attempting to use the input. Since scanf() returns the number of successful assignments made, this value should be 3:
#include <stdio.h>
#include <string.h>
int main(void)
{
char a[100], b[100], c[100];
printf("Enter alien names:\n");
int ret_val = scanf("%99s %99s %99s", a, b, c);
if (ret_val == 3) {
printf("The alien names are %s, %s and %s. A meteor hit %s's "
"spaceship. A star scratched %s\'s spaceship. But %s "
"fixed %s and %s\'s spaceships. The three became friends "
"and are from the planet BYG (which means BLUE YELLOW GREEN)\n",
a, b, c, a, b, c, a, b);
} else {
puts("Input error");
}
}
What is the specific reason for the runtime error I'm getting here?
The function scanf using the format specifier %s expects to be passed the address of a char array, in which to place the input data. For example an array such as
char a[100];
However, you pass simple char variables a and b and c which can hold values in the range -128 to 127, or 0 to 255, depending on whether the implementation's char is signed or unsigned.
These variables were not even initialised, so indeterminate values were passed to scanf. But even if they had been initialised, it is very likely that the values passed will cause a segfault, when used as addresses.
My compiler issued 2 warnings for each of a, b and c passed to scanf.
warning C4477: 'scanf' : format string '%s' requires an argument of type 'char *', but variadic argument 1 has type 'int'
warning C4700: uninitialized local variable 'a' used
Please enable and act on all compiler warnings.
//There are things that shoudn't be there. Im not a pro but this is what I think.
#include<stdio.h>
#include<string.h>//you have include this library but you didn't use a function from it.
//I think what you want to do is use the str functions like strcpy
//but in this case you don't need to use it.
void main()
{
char a[25],b[25],c[25];//Here you declared a character a, b and c. But if you want to store a string, you have to declare an array of characters. So instead of a, b, c, it's a[someValue], b[someValue] and c[someValue].
//Declare an array with a size that you think will cover the whole "alien name". e.g. a[25]..
//but i don't know, maybe you did it on purpose. Maybe you just want to name the aliens with one character like A, B, C. But if you want to name the aliens with a long name, you must declare an array.
printf("Enter alien names:\n");
scanf("%s\n%s\n%s\n",a,b,c);//You don't need to put the "\n" between those "%s". "\n" means "newline". It will work without it because scanf automatically reads next set of characters when it meets white space of newline.
//--so you can remove "\n" in there and replace it with space. But you can leave it there also but you really have to remove the last "\n" because scanf will search again for the next
//--new line before it will end asking for input and pressing enter will not work because you have to type another set of characters before scanf will read the last "\n" that you put at scanF.
//Another mistake here is the format specifier that you used (%s). It doesn't match declaration because you declare char a, b, c, that will only store one character each.
//In case that you're really just storing one character each alien's name, you have to use the "%c" instead of "%s" and you must pass the reference of the char variable in
//--scanf, e.g. scanf("%c %c %c", &a, &b, &c);
//Just remember that if you plan on storing a string or a long name there, you must declare an array like I said at the beginning.
//--and if it's an array, you don't need to include the '&' on every variable when you're passing it in scanF.
//There's nothing wrong here if you're alien's names are string.
printf("The alien names are %s, %s and %s. A meteor hit %s's spaceship. A star scratched %s\'s spaceship. But %s fixed %s and %s\'s spaceships. The three became friends and are from the planet BYG (which means BLUE YELLOW GREEN)",a,b,c,a,b,c,a,b);
}
The specific reason for the runtime error is this line:
scanf("%s\n%s\n%s\n",a,b,c);
The %s conversion specifier tells scanf to read a sequence of non-whitespace characters from the input stream (skipping over leading whitespace) and store that sequence to an array of char pointed to by the corresponding argument. The problem is that a, b, and c are not pointers to char; they're single char objects that haven't been initialized. The odds of any of them containing a value that corresponds to an address that scanf can write to is almost non-existant.
First, change the declarations of a, b, and c tochar a[SOME_LENGTH] = {0}; // initialize array contents to 01
char b[SOME_LENGTH] = {0};
char c[SOME_LENGTH] = {0};
where SOME_LENGTH is a number that's long enough to contain the longest string you expect to enter plus one extra space for the string terminator. IOW, if the longest string you intend to read is 10 characters long, then your declarations need to be
char a[11] = {0};
char b[11] = {0};
char c[11] = {0};
Secondly, change your scanf call to
scanf( "%(SOME_LENGTH-1)s %(SOME_LENGTH-1)s %(SOME_LENGTH-1)s", a, b, c );
where (SOME_LENGTH-1) is the length of your buffer minus 1. Again, assuming SOME_LENGTH is 11:
scanf( "%10s %10s %10s", a, b, c );
This will help prevent a buffer overrun in the event you enter a string longer than what the buffer is sized to hold.
Both the %s conversion specifier and a blank space in the format string tell scanf to consume and discard any leading whitespace. You can run into trouble specifying whitespace characters in the format string.
Additional notes:
main returns int, not void - change your main to
int main (void)
{
...
}
If there are fewer elements in the initializer than there are in the array, then excess elements are initialized to 0. So in this case, the first element is *explicitly* initialized to 0, and the remaining elements are *implicitly* initialized to 0.
I had a project to write this program that reads a character, integer and a floating number. It also had to convert the character in to its ASCII integer. I vaguely understand most of it except the code regarding the ASCII number. I created most of it on my own but when it came to converting the character I had a buddy help me, but he is not the best at explaining this.
Any explanation would be very helpful, thank you. I did this all by trial and error for... probably far too long :P
#include <stdio.h>
#include <stdlib.h>
int main(void)
{
char c;
int i;
float f;
printf ("Please enter a character: ");
scanf ("%c", &c);
printf ("Please enter an integer: ");
scanf ("%d", &i);
printf ("Please enter a floating point number: ");
scanf ("%f", &f);
printf ("\n");
printf ("The character you entered is: %c which is %d in integer-specification\n", c,c);
printf ("The integer you entered is: %d.\n", i);
printf ("The floating-point number you entered is: %f.\n", f);
return 0;
}
It will be helpful to have a reference documentation of printf handy.
When the format specifier is %c, printf expects an int. A char works since it is promoted to an int.
When the format specifier is %d, printf expects an int. A char works since it is promoted to an int.
For the first case, printf prints the character corresponding to the value of the int.
For the second case, printf just prints the number.
Essentially a char is just an integer with a range from 0 to 255, the only thing that makes it a 'character' is that we have assigned characters to be represented by certain numbers.
What's going on in the printf() is that first you tell it that you're going to pass a char and would it please just output that byte to be displayed, then you say that you want it to convert an integer to a string and output that.
What it boils down to is that the ASCII code is the character.
Note: for reasons that are not important at the moment when being passed into a vararg function like printf() chars and shorts are promoted to ints.
Here is my attempt at explaining this.
Everything in a program memory is stored as sequences of 0s and 1s (binary numbers). You are probably familiar with bits and bytes, but just in case: a binary digit (0 or 1) is a bit. A sequence of 8 bits is a byte. Characters, such as 'A', 'b', '1', etc. have to be stored as numbers in memory. There are different ways to map a character to a number: EBCDIC (very rare these days, was used on large mainframes in the old days), UTF-8, UTF-16, UTF-32 (types of Unicode), ASCII. These mappings are called character encodings, and ASCII is the simplest of those commonly used.
So, when you enter a character, it gets stored in the variable c as an integer number encoded using ASCII. The content of memory location corresponding to the variable can be thus viewed both as a character and an integer.
When using the printf() function you can request the same variable to be printed using different possible representations. In this case, since c is a character variable and can be represented as a character or a number, you can use the different format specifiers, %c and %d, to have it printed as character and integer, respectively.
The 1st of the printf() calls above takes 3 arguments. The first argument is a string that is printed out, with things that start with % being used to interpret the remaining arguments. %c corresponds to the 2nd argument, %d to the 3rd. %c says: "treat the 2nd argument as character and print it out." %s says: "treat the 3rd argument as integer and print it out."
The other 2 printf() calls in your code take only 2 arguments. The 1st argument, the string, contains only one thing starting with % (format specifier), so we only need 1 additional argument to be interpreted using the format specifier.
Hope this is helpful.
the Man ascii will make you understand
Practice.c
#include <stdio.h>
main()
{
char a;
printf("\nEnter Anything = ");
scanf("%c",&a); <Line 1>
printf("\n%d",a);
printf("\n%c",a);
}
Output 1 : Enter Character = 5
53
5
Output 2 : Enter Character = a
97
a
This program gets executed exactly by the book.
New.c
#include <stdio.h>
main()
{
char a;
printf("\nEnter Character = ");
scanf("%d",&a); <Line 1>
printf("\n%d",a);
printf("\n%c",a);
}
Output 1 : Enter Character = 5
5
♣
Output 2 : Enter Character = a
0
This is the same program as Practice.c with minor change in it. It is not a question but I mistakenly typed %d instead of %c in the line denoted by Line 1 of the program. This mistake of mine produced 2 very different outputs. What is the exact reason behind it?
Below ASCII 32, all are non-printable characters. In second code you are reading an int and then trying to print the equivalent character which is non-printable.
For the second input a, scanf doesn't read this character and leave it in the buffer because it expects an integer not a character. The variable a is uninitialized and you are now accessing an uninitialized variable. This invokes undefined behavior.
The character data type is having size 1 byte, whereas integer is usually 4 bytes. Here you have tried to read into a character variable an integer. There is not enough storage to handle this properly. The result depends on whether your architecture supports little endian or big endian notation.
When you use %c the input is taken as character and stored its ASCII value.
When you use %d the input is taken as integer.
When you print with %c, it tries to print ASCII char at given value.
When you print with %d, it tries to print the number.
What really happened in your NEW program is
scanf("%d",&a);
Format specifier while reading is given as an integer %d ,so the compiler assumes the input value as integer even though it is stored in char variable, so the value of variable will be
a = 0x05 which is an integer 5
printf("\n%d",a);
printing variable a as integer prints 5 on output
printf("\n%c",a);
I think you know that while reading a digit as a character(using %c) it's ASCII value is stored (for eg: scanf("%c",&a)); and you enter a as 5, the value stored in the variable a is a=0x35 in hex ,or 53 as integer representation
printing variable as character-> since 0x05 is not character or digit in ASCII value it prints the special character on the output
for about ASCII table refer : http://www.asciitable.com/