I am having problems using the atoi() function where i have 2 char arrays which i want to turn into integers. So say
Doing a print on newWindow gives me a value of = "1234009" and newSize = '90'. Do I have to close atoi? It seems like its appending everything to the same value. Which is not what we want.Code:char window[4] = ('1','2','3','4') char size[4]= ('0','0','9','0') newWindow = atoi(window); newSize = atoi(size);
Thanks
Yep, because window is not a C string and atoi() operates on C strings. A C string is a sequence of characters with '\0' (the null terminator) at the end.Originally Posted by TaiL
The reason for this is that the program does not "know" how long the string is supposed to be (even if you give it a declared length); it just keeps reading until it hits \0. This may seem silly but it makes sense from a performance stand-point; it would be less efficient if the processor had to look-up the length of a string and do a comparison every byte to see if it had reached the end.
What is happening with the above code is the program puts two variables into memory, window and size. Window is 4 bytes (1234), and obviously the next thing in memory is size (0090).
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
thanks. MK wasted an hour trying to figure it out, who woulda known all i needed was a NULL at the end of my . Thanks again.
Don't think of stuff like that as a waste, think of it as a mnemonic aid
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
