I think it's rather a stretch to refer to segment:offset as "not actually a location in memory". (And by "rather a stretch" I mean "completely dishonest".) (Unless you've got another post other than the one I know of, in which case you need to cite it.)Originally Posted by Overworked_PhD
I am not the one acting like a douche. I am trying to help as many people as I can that have questions on this forum. You on the other hand only respond to threads I post in a futile attempt to show that you are more educated than me on the subject, which you are not. Yes, I will counter your stupidity at anytime you try to mislead the people I help with your almost absent C knowledge.
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 think the point is, he is using double* as an abstract representation of an address. Sort of like how ANSI/ISO C uses the term 'object' as an abstract representation of a variable. Most people though just like to think in things they can relate to and not think in terms of an overall general case.
LOL.
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 don't see anything funny about this. Remeber, C is supposed to be portable. So how does one go about defining the rules for a portable language? By writing in generalized terms.
No, I was just laughing because what you said showed no understanding of what the person you were quoting actually said. Why don't you run off again and open the C book at the Chapter called : "Pointers" and read the first line there about what a pointer really is.
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.
Kernighan and Ritchie Chapter 5: Pointers, Line 1:
"A pointer is a variable that contains the address of a variable."
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 definition has been superceeded by the ANSI/ISO one.
Eric is speaking in terms of the modern standard you halfwit.
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.
If indeed it held a VALUE like you claim, please enlighten me, what value does a void* hold?
I'll wait for you to run back to your daddy to provide an answer.
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.
Huh? Can you please that in proper English. Also, please cite the passages that explicitly state a pointer must hold an address because I don't see it.
You mean the Kernighan and Ritchie???!
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
No, I "can't please that in proper English". Maybe you can.
Anyway, stop avoiding the question. What type of "value" does a void * point to, according to your interpretation?
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 they wrote this in a book???!
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
Yes, that's chapter 5 line 1 of the original K&D book.
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.
