Your response to pointers is wrong in concept.
Your response to members is wrong entirely.
As for pointers, you gave basically a textbook definition of how they are used, but not really what they are. They are nothing but integers whose values can be interpreted as an address. Their sizes change between platforms but to keep things simple we should assume Windows x86 (32-bit pointers).
0x00000100 can’t be a pointer but 0x00400000 is. It is simply a value that points to valid memory. Though some values that are meant to be pointers could point to invalid memory if your program has errors.
Members are “attributes” of classes. You posted an example in which a function was declared inside another function. This is entirely illegal.
For this, you need to redo some of your learning.
L. Spiro
Show differencesHistory of post edits
#2L. Spiro
Posted 02 September 2012 - 07:44 AM
Your response to pointers is wrong in concept.
Your response to members is wrong entirely.
As for pointers, you gave basically a textbook definition of how they are used, but not really what they are. They are nothing but integers whose values can be interpreted as an address. Their sizes change between platforms but to keep things simple we should assume Windows x86 (32-bit pointers).
0x00000100 can’t be a pointer but 0x00400000 is. It is simply a value that points to valid memory. Though some values that are meant to be pointers could point to invalid memory if your program has errors.
Member are “attributes” of classes. You posted an example in which a function was declared inside another function. This is entirely illegal.
For this, you need to redo some of your learning.
L. Spiro
Your response to members is wrong entirely.
As for pointers, you gave basically a textbook definition of how they are used, but not really what they are. They are nothing but integers whose values can be interpreted as an address. Their sizes change between platforms but to keep things simple we should assume Windows x86 (32-bit pointers).
0x00000100 can’t be a pointer but 0x00400000 is. It is simply a value that points to valid memory. Though some values that are meant to be pointers could point to invalid memory if your program has errors.
Member are “attributes” of classes. You posted an example in which a function was declared inside another function. This is entirely illegal.
For this, you need to redo some of your learning.
L. Spiro
#1L. Spiro
Posted 02 September 2012 - 07:44 AM
Your response to pointers is wrong in concept.
Your response to members is wrong entirely.
As for pointers, you gave basically a textbook definition of how they are used, but not really what they are. They are nothing but integers whose values can be interpreted as an address. Their sizes change between platforms but to keep things simple we should assume Windows x86 (32-bit pointers).
0x00000100 can’t be a pointer but 0x00400000 is. It is simply a value that points to valid memory. Though some values that are meant to be pointers could point to invalid memory if your program has errors.
Member are “attributes” of classes. You post an example in which a function was declared inside another function. This is entirely illegal.
For this, you need to redo some of your learning.
L. Spiro
Your response to members is wrong entirely.
As for pointers, you gave basically a textbook definition of how they are used, but not really what they are. They are nothing but integers whose values can be interpreted as an address. Their sizes change between platforms but to keep things simple we should assume Windows x86 (32-bit pointers).
0x00000100 can’t be a pointer but 0x00400000 is. It is simply a value that points to valid memory. Though some values that are meant to be pointers could point to invalid memory if your program has errors.
Member are “attributes” of classes. You post an example in which a function was declared inside another function. This is entirely illegal.
For this, you need to redo some of your learning.
L. Spiro