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
1. Get rid of gets(). Never ever ever use it again. Replace it with fgets() and use that instead.
2. Get rid of void main and replace it with int main(void) and return 0 at the end of the function.
3. Get rid of conio.h and other antiquated DOS crap headers.
4. Don't cast the return value of malloc, even if you always always always make sure that stdlib.h is included.
You made the following statements
Now, for the second time, I'm asking you to back up this claim by citing the passages in ANSI/ISO C that explicitly state that a pointer must hold an address.First, don't call him Eric. As I said before, he is not your buddy. Secondly, the ANSI standard doesn't define a pointer as a data type not holding an address.
1. Get rid of gets(). Never ever ever use it again. Replace it with fgets() and use that instead.
2. Get rid of void main and replace it with int main(void) and return 0 at the end of the function.
3. Get rid of conio.h and other antiquated DOS crap headers.
4. Don't cast the return value of malloc, even if you always always always make sure that stdlib.h is included.
No I can't quote it because I am not even going to bother searching for it. You know why? Because a pointer is a data type that HOLDS AN ADDRESS you idiot! Read my lips: Pointer = addres. Did you catch that yet?
1. Get rid of gets(). Never ever ever use it again. Replace it with fgets() and use that instead.
2. Get rid of void main and replace it with int main(void) and return 0 at the end of the function.
3. Get rid of conio.h and other antiquated DOS crap headers.
4. Don't cast the return value of malloc, even if you always always always make sure that stdlib.h is included.
I am not going to provide any evidence to my claims because I will get you into a bad habit of asking for evidence for VERY OBVIOUS THINGS like why 1+1 equals 2 in base 10. So why don't you prove me wrong instead? Give me a pointer that doesn't hold an address and I will believe you. Until then, you remain the same impotent C programmer I've known.
1. Get rid of gets(). Never ever ever use it again. Replace it with fgets() and use that instead.
2. Get rid of void main and replace it with int main(void) and return 0 at the end of the function.
3. Get rid of conio.h and other antiquated DOS crap headers.
4. Don't cast the return value of malloc, even if you always always always make sure that stdlib.h is included.
And for people like laserlight and MK27, please don't help this guy out. Let this guy do his own homework.
You claim some fictitiously usenet post, that you don't actually cite, and hold that as a credible source, but discredit probably THE most popular C book, choosing to believe your fake ass usenet post by someone less known than the authors of said book.
Nice job, troll. Let's make the ban permanent this time, since you add nothing of value to any conversation, and continually try to hijack newbie threads to confuse them.
Quzah.
Hope is the first step on the road to disappointment.
1. Get rid of gets(). Never ever ever use it again. Replace it with fgets() and use that instead.
2. Get rid of void main and replace it with int main(void) and return 0 at the end of the function.
3. Get rid of conio.h and other antiquated DOS crap headers.
4. Don't cast the return value of malloc, even if you always always always make sure that stdlib.h is included.