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.
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.
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.
Well, the standard does not say that not saying something makes it false, just that the standard doesn't promise it's true. Of course, if you were to do some more in depth analysis (which the standard is not all that interesting) you might be able to demonstrate something logically about a pointer being equivalent to a memory address.
BUT, IMO memory addresses are not really significant in normative C programming. What is significant it the concept of "reference to" an existing entity of some type.
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
So in other words, you aren't going to tell us what's up.
I don't know what you're problem is specifically with me but I just want to understand what you're talking about. Don't get bent out of shape about what side I'm on, I think you're older than that. I'm simply asking for additional knowledge and if you don't want to share it then kindly don't bring it up in a public forum to brag.
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.
> Maybe when I wake up in the morning, I will see the significance of it.
Actually bub, all you're going to see from now on is 6 letters beginning with 'b'.
Consider this an opportunity to be less overworked.
Bye troll.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Uhh... Am I still in the right thread?
But seriously, could someone give me an answer so I can see where I'm going wrong please?
ÉireKarl, I apologise on behalf of this community for the mess that this thread has become. I am going to close this thread. I suggest that you start a new one with your current question.
Look up a C++ Reference and learn How To Ask Questions The Smart WayOriginally Posted by Bjarne Stroustrup (2000-10-14)