ASCII C Help, Please
Hi I have had some problem with these functions I am using to write a program that is supose to ask the user for his/her first and last name and then accept input and store it in a string array, and then print it to the screen. I can do it C++ but C is different so any help is appreciated thank you.
Code:
#include<stdio.h> |
just breifly looking at it have not done c in awhile but I don't know if c recognizes the new commenting // try using the old style */ it may be having trouble interpreting the comment styles...
KC |
Quote:
So it's not the comments but something else, I don't exactly know what but when you compile it compiles fine although the out-put is unexpected. |
Hmm maybe try using the string lib.
#include <string.h> and int main (void) KC |
Yes, you need "#include <stdio.h>" for "printf()", "scanf()", "getchar()" and friends, and "#include <string.h>" for "strcat()". But generally I'd expect these to be warnings - not fatal errors.
And I don't see anything in your source that would cause a crash. So what exactly is the problem: is it a compile error? A runtime error? Can you cut/paste the error message? It basically looks OK. Good job, really ;-) |
Quote:
|
No, kenkaz misspoke himself slightly.
"string.h" is a header, not a library. You #include <string.h> before you compile your program. We're assuming that maybe you got a compile error (or warning) complaining about "strcat()", which is one of the string-related functions declared in string.h. |
Quote:
Code:
#include<string.h> Code:
strcat(fullName, firstName, lastName); |
hiho
first do on top of your code: #include <string.h> and replace strcat(fullName, firstName, lastName); with strcat(fullName,firstName); strcat(fullName,lastName); but for such things i like sprintf(); more because you can easily format your string: sprintf(fullName,"%s %s",firstName,lastName); just because of safety: you have a buffer overflow problem in your prog e.g. what if the user enters more than 21 characters for his name? or to be more correct, if the user enters more than 42 characters you get a segmentation fault because sscanf wants to read from stdin but the buffer it want's to write in (firstName and lastName) are 42 characters in size so sscanf would write to a buffer where it isn't allowed to to be more safe replace sscanf(); with fgets(firstName,21,stdin); and fgets(lastName,21,stdin); greetz |
Quote:
PS: In most environments I know of, "strcat()" is declared in "string.h". If you try to compile a C++ program that uses "strcat()" on one of those platforms, the compile will die a fiery death. So it was a reasonable guess on our part. And I hope you're clear about the difference between a compile-time header, a link-time library, and a runtime error. Apparently you're experiencing a runtime error. We're eager to hear exactly what that error is! PS: "man strcat" in a Linux environment should give you the prototype for "strcat()". It takes two arguments, not three. But I *don't* know if that would necessarily cause your crash. PPS: If you're on Linux, try compiling with "gcc -g ..." and running the program under the gdb debugger. |
The error I got, as I said was a run time error. This is basically what happened, I compiled and ran the program and typed my full name into char firstName[21]; char lastName[21]; and once I hit enter for it to display my name I got a bunch of characters that were not part of the alphabet or even part of the numerical system.
I mean it was supose to display my name. Anyway I done something similar to what Thinking said and it worked fine. But still out of interest is it so that strcat() can only take 2 parameters? And just out of interest again, will I ever need these console functions later on in life when I'm a professional programmer? |
well i understand your runtime error but i don't really know what could cause the problem in your code
i didn't have this on my suse linux as you said you get some crazy numbers and characters after you entered the lastName this means that your printf(); does something strange it's caused because you overwrote the ending binary 0 from the fullName string so printf(); didn't know where the end of the string is and it printed what was in memory after the fullName string maybe it would work if you initialize your arrays: char firstName[21]={0}; char lastName[21]={0}; char fullName[50]={0}; btw: yes, strcat only takes 2 arguments it concatenates the 2 strings char *strcat(char *dest, const char *src); if you have "hello" in buffer dest and " world" in src then after strcat you have "hello world" in dest! and it returns dest and for your second question: hmm good question i would say yes BUT if you get better you can solve problems that are more complex than what you prog now so yes, i think you will use them in future too, but in future there will be no problem for you to use them! it will be as simple as to pick one's nose *g* greetz |
why use such puny buffers?
char [21] ??? how many million bytes have you got spare on your computer? give yourself some rooooom. ;) |
Looks to me like your problem is here:
Code:
strcat(fullName, firstName, lastName); Code:
strcat(fullName, firstName); The strcat() function concatenates the second string onto the end of the first string, and it works by finding the terminating 0 character in the first string and then copying the second string to that location. But you did not initialize the data in fullName to anything before passing it to strcat(); so whatever garbage was in memory in the location that fullName happens to be in is what's there when you call strcat() on it, and there is most likely a lot of junk before the first random 0 occurs. You'd need to do something like this: Code:
fullName[0] = 0; Your buffers are small, but that is not the source of your problem assuming you are typing less than 20 characters in for your first and last names. Not many people have a first or last name longer than 20 characters so anything larger would probably be overkill. Additionally, if you want to play it safe, you can prevent overruns with scanf like this (once again, this is probably not the source of your original problem, but it's just if you're curious): Code:
char somebuf[21]; Jason |
you haven't initialised your char buffers.
Code:
char firstName[21]; so when strcat comes along it cats stuff onto the random data. I would put them outside the main, then they will be static buffers and intialised to zero. Usually best to put buffers in static data rather than stack data as they are generally larger storage areas. and give them size, man. Code:
#include<stdio.h> |
oooops! didn't test ;)
strcat changed: Code:
#include<stdio.h> |
hmm
just a little question what does fflush(stdin); ?? fflush flushes an output buffer but stdin is input so it should just do nothing, not? |
'tis removed.
good spot. (cut and pasted) |
I know that when you want to put a value into a variable using scanf you need to use the & operator like:
Code:
scanf("%d", &age); Also do I need to use the & operator for arrays when accepting string input using scanf? |
for an array don't need the &
the name is the address. e.g: char buffer[100]; buffer same as &buffer[0] |
Quote:
I know that the & symbol before a variable like: Code:
&myAge; Thank Yous For You Time :) |
correct.
trying getting familiar with a debugger. 'gdb' with 'ddd' is particularly good. you can play about and see what's really happening in there. It all helps gain an understanding. you can even call functions etc. |
Have another question. What I am trying to do with the below program is to not print any of the array on the last string literal, but still have the %4s in the string.:
Code:
/* |
printf("How do get this to print and not the array? >> '%%4s' ");
PS: Leaving out the "#include <string.h>" (from the earlier version, when you had "strcat()") and failing to return a value from "main()" (still in the current version) are both arguably bugs. At best, they're poor form. The "fflush()" is harmless, but unnecessary. The C library automatically flushes any output pending on "stdout" before accepting input from "stdin". The third stream, "stderr", is always unbuffered and, consequently, never needs to be flushed. As a previous poster suggested, the debugger (e.g. "gdb") can be your friend. On gcc, debugging support is enabled via the "-g" compiler switch. Another good practice is to always compile with "full warnings". On gcc, this is the "-Wall" switch (actually, there are also other, even stricter switches you could add). Here's what I got compiling your program with "-g" and "-Wall": Quote:
|
Code:
printf("How do get this to print and not the array? >> '%4s' "); e.g Code:
printf("How do get this to print and not the array? >> '%4s' ","bye bye"); |
i think InivisbleSniper wanted to know this:
printf("How do get this to print and not the array? >> '\%4s' "); in C you have to use a backslash for the % if you do printf("\%"); it will print the % printf("\\"); will print a \ and so on .... if you aren't sure ask yourself this question: if i want to print %4s how does the printf function know if i want to print %4s or a string? it's the backslash who makes the difference *g* |
this?
Code:
int main(void) |
Can someone please tell me where I can learn more of the "Standard ANSI C Functions". Something that is more informitive, has more discription then other tutorials?
|
here's a very good C book, includes ASCII to decimal conv table and lists+definitions of std includes eg stdio.h, strcat() etc.
|
Quote:
Also I was wondering how do I accept user input for a "char". I mean accept user input for just one character no more and no less. I have a program that is not working because of this. It gets up to the part where the user is supose to enter a S for single or a D for double. But then it crashes, if someone could tell me how to fix this program without including any new functions that I don't know about yet, that would be very helpful. Code:
#include<stdio.h> Thank You. |
When scanf-ing into a numeric type like char, remember to put "&" in front of the variable. Otherwise, you will have a serious bug (that most compilers will never catch!). Also, you can't really say char c = " " because " " is a string, not a character. Maybe you meant ' '. Your compiler should at least have warned you about that.
|
Thanks, I fixed it up now :)
cheers |
Sorry for the double post but this thread was more appropriate then opening an entirely new one.
|
Kernighan and Ritchie.
C programming language I usually use the man pages. |
All times are GMT -5. The time now is 08:17 PM. |