ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I realize the difference between a char and a char*, I guess I just dont see when each one applies. A lot of the time in my notes from various classes, the prof's always seem to use char*'s as parameters and then randomly pick and choose between char's and char*s whenever declaring variables. But whatever, thanks for your help.
I also tried writing and compiling your code from the above reply and still recieved the same error message, so it must be the compiler at school.
You'll get the error with gcc if you don't #include <stdlib.h>. The reason is because without the malloc() prototype the return type defaults to int instead of void * like it's supposed to be. If you #include <stdlib.h> the error/warning should go away.
char and char * are definitely very much different. It would be a very lengthy topic for me to get into, but a google search on pointers in C should reveal a lot.
It's usually a good idea to cast the return value of malloc to whatever pointer you're trying to make. A void *, which malloc returns, can't be dereferenced by itself and needs to be cast before dereferencing. I'd recommend changing your code to read:
If you code in C, it's not a good idea to cast the return value of malloc(), it's actually
a bad idea because will hide any failure to include the header where malloc() is declared,
In C++, on the other hand, you must cast what malloc() returns because C++ won't perform
that conversion automatically as C will. But if you use C++, you should always use new and
delete when allocating memory dynamically.