Timeline for Issues on using pointers
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2022 at 15:42 | review | Close votes | |||
| Aug 7, 2022 at 0:02 | |||||
| Aug 3, 2022 at 15:27 | history | edited | Joel Bodenmann | CC BY-SA 4.0 | remove superfluous text and improve formatting |
| Aug 3, 2022 at 15:25 | comment | added | jarmod | See Does stack grow upward or downward? | |
| Aug 3, 2022 at 15:23 | comment | added | r043v | pointer is a var himself and so on have a dedicated address where it store the pointed address. so, 0xffffcbe0 hold your pointer data and his content store 0xffffcbec. it seem that the linker has stored pointer var before your int in your program memory, all is nice. | |
| Aug 3, 2022 at 15:22 | comment | added | William Pursell | The reason it prints 0xffffcbe0 for the address of pnum is because the address of pnum is 0xffffcbe0. | |
| Aug 3, 2022 at 15:16 | answer | added | Some programmer dude | timeline score: 4 | |
| Aug 3, 2022 at 15:11 | comment | added | tkausl | I want to know the reason. The reason for what? Its quite unclear what you're asking. | |
| Aug 3, 2022 at 15:10 | history | edited | Some programmer dude | CC BY-SA 4.0 | added 66 characters in body |
| S Aug 3, 2022 at 15:08 | review | First questions | |||
| Aug 3, 2022 at 15:32 | |||||
| S Aug 3, 2022 at 15:08 | history | asked | Trevor Song | CC BY-SA 4.0 |