Editing Talk:138: Pointers
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 3: | Line 3: | ||
Wait until he finds out they're codes for that old saving system. 21:42, 3 June 2013 (UTC) | Wait until he finds out they're codes for that old saving system. 21:42, 3 June 2013 (UTC) | ||
− | Or perhaps the Black Hat | + | Or perhaps the Black Hat _is_ answering the question but in an obscure way. The addresses might be pointing to the locations where the game keeps its important information (such as the score count or the level), so it can be cheated by changing the data at these locations. |
− | + | ||
The problem with 0x-1 is not that it's missing digits, it's that the memory in the computer is represented as a closed loop. So if you try to go back to the cell "before the first cell", you will really access the last cell, 0x-1 really equals to 0xFFFFFFFF in the 32-bit address space. Evidently, Cueball had found a way around this only it didn't quite work out. (People deeply interested in the workings of the pointers should also read about the memory protection modes and alignment requirements, both of which might interfere with reading from the address 0xFFFFFFFF.) [[Special:Contributions/108.162.246.5|108.162.246.5]] 00:33, 28 January 2014 (UTC) | The problem with 0x-1 is not that it's missing digits, it's that the memory in the computer is represented as a closed loop. So if you try to go back to the cell "before the first cell", you will really access the last cell, 0x-1 really equals to 0xFFFFFFFF in the 32-bit address space. Evidently, Cueball had found a way around this only it didn't quite work out. (People deeply interested in the workings of the pointers should also read about the memory protection modes and alignment requirements, both of which might interfere with reading from the address 0xFFFFFFFF.) [[Special:Contributions/108.162.246.5|108.162.246.5]] 00:33, 28 January 2014 (UTC) | ||
Line 30: | Line 30: | ||
I moved the title text explanation to the main one. Seems to make more sense that way. [[User:Dontknow|Dontknow]] ([[User talk:Dontknow|talk]]) 23:35, 17 April 2017 (UTC) | I moved the title text explanation to the main one. Seems to make more sense that way. [[User:Dontknow|Dontknow]] ([[User talk:Dontknow|talk]]) 23:35, 17 April 2017 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |