Prove that the offsets are not memory addresses. Prove that you do in fact just use offsets. Prove what the offsets are offsets of.
You made a claim, I'm calling you out on it now, like you did earlier. You made the claim, now prove it.
Quzah.
Prove that the offsets are not memory addresses. Prove that you do in fact just use offsets. Prove what the offsets are offsets of.
You made a claim, I'm calling you out on it now, like you did earlier. You made the claim, now prove it.
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.
No, in fact I provided a bunch of evidence to support your claim that the standard does not simply define a pointer as memory address, if you check post #77.
Just I don't think it is incompatible with defining a pointer as a memory address either. In reality, all real pointers could both conform to the definition in the standard and contain memory addresses. But the standard's definition is slightly more "conceptual".
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
Come on Overworked. Run over to Dr. Whatamaniuk at Kodak to tell us all off.
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.
I was being sarcastic. Now, the point is than an address is a concrete example of a pointer. Just like how the velocity of an object at a specific time is a concrete example of the derivative. In both cases, they are specific cases of a more abstract/general concept. To say that in either examples, the specific cases constitute the exact definition, is just plain wrong.
Last edited by Overworked_PhD; 05-01-2010 at 08:35 PM.
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.
Prove that the offsets are not memory addresses. Prove that you do in fact just use offsets. Prove what the offsets are offsets of. Stop skirting around the issue. Prove your claim, or issue the appropriate apologies, and shut the .... up.
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.
This is the same reason why the standard uses the term 'object' instead of 'variable'. This is because a variable is a specific example of an object. However, there are objects, that aren't variables. For example, what gets returned by malloc().
Last edited by Overworked_PhD; 05-01-2010 at 08:54 PM.
You didn't exactly help me understand that when I asked what pointers hold instead of addresses. You just said that they held offsets, which doesn't make any sense, because on my machine I can also store some offset of an array in a pointer, and that pointer will contain an address. So that is inherently confusing. If you wanted to argue that one example was fairer to the general concept in terms of the Standard, then feel free to argue that, but I don't think it's "just plain wrong" to sick to the concrete things in life.
Every modern computer has memory in terms of cellular arrays that are numbered and these numbers are addresses. (Even though physical addressing is rarely used in anything recent, to allow programs to access additional memory on the hard drive or other device, which is important to systems with low RAM space.)