Uhh.. yeah I said you were wrong in that, you said a pointer does not point to an address. Also, I you commented on one of my posts not the other way around, so you need to prove me you are right, which of course you are not. So run back to daddy and get your ass wiped by the usenet boys who actually know what they are talking about Chad. Also, stop drinking!!!Originally Posted by Overworked_PhD
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.
Just to be clear, I was not disagreeing with K&R.
But here's the closest thing I found to "the definition of a pointer" in the c99 draft standard:
from539 — A pointer type may be derived from a function type, an object type, or an incomplete type, called the referenced type.
540 A pointer type describes an object whose value provides a reference to an entity of the referenced type.
541 A pointer type derived from the referenced type T is sometimes called “pointer to T”.
http://c0x.coding-guidelines.com/index.html
sec 6.2.5 Types
Because the standard does not deal with it's own implementation, I think the language (of the standard) does not permit a definitions such as "contains an address of". Technically, a compiler could do this however it wants -- it could release passenger pigeons and upon their return provide "a reference to an entity of the referenced type".
Still, methinks this most likely a memory address...hence, it would be hard to prove "contains an address of" false (the standard doesn't).
Last edited by MK27; 05-01-2010 at 07:20 PM.
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
I interpreted that to mean that you are the one making the extraordinary claim that pointers do not have to store addresses. Well do you know what they store instead? Perhaps I've misunderstood, but I hope this isn't some semantic distinction between memory locations and object offsets, or something. TBH I'm not even sure if that distinction is real. Memory is frequently the only resource that matters.
Again, quit side stepping the issue and cite the exact ANSI/ISO C passages that explicitly state that a pointer must hold an address. I mean, if you are going to say I'm wrong, at least have the proof. Otherwise just shut up and go take care of your snot nosed punk kids. I mean, you seem to spend more time on here than with them. At this rate, they will probably end up doing drugs because "dad was never around."
Well, I think the best way to get an impression over how this started is to go back to page 2 of this thread and read on from there. Make sure you grab some popcorn.
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.
Lol... you mean like you ended up? Nah.. my kids are doing great, actually my eldest son is just learning C, if you want I can arrange for him to teach you a few things.
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.
Some of the SUN Machines at Kodak use an offset, and not an address, when it comes to stuff like indexing arrays.
Cite the exact usenet post, and the credentials of the poster, and the ANSI/ISO C passages that explicitly state that a pointer doesn't hold an address. Since you are the one claiming it does not, prove it. Also, prove what it does in fact hold, if it does not in fact hold an address.
While you're at it, grab a dictionary, and look up the word address to understand its meaning.
Quzah.
Hope is the first step on the road to disappointment.
Again the Kodak standard. ROFL
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.
<giggle> <burp>Make sure you grab some popcorn
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
Prove it.
Quzah.
Hope is the first step on the road to disappointment.
No, it's a standard SUN Machine with a conforming C compiler. It would only be a Kodak standard if the company had modified the compiler.
I know man. Are you that pathetic that you don't realize everyone is just making fun of you here?
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.
Yes, because it's totally obvious that both MK27 and whitefang has sided with you.
Lol they haven't sided with anyone. They are just sane, unlike you madman!
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.
