Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Clarifications / Corrections on the ExpansionPak Video.
- Credit to N3rdswithgame (https://twitter.com/n3rdswithgame) who approached me regarding this matter. Whilst I aim to make my content as accurate as possible, everyone has flaws and I'll hold up my hands to any inaccuracies that are presented in any of my videos.
- POINTERS
- No pointers would have been hard coded at all, all of them being determined at either runtime or set by the "linker". If the myth was true, then the pointers set by the linker would require very little modification and likely a small amount of testing to verify. Those set at runtime would have been determined by the allocation algorithm, and therefore would not have been affected should the myth be true (It isn't true).
- MEMORY ALLOCATION
- This is something that I failed to expand on a tonne because I didn't want to overcomplicate the matter. Whilst some allocation would have been hardcoded (as some areas of memory are static), the dynamically allocated areas of memory would have not been hardcoded at all.
- GAME CODE
- The jump instructions would not have been written by hand but instead written by the compiler from C (The programming language) to MIPS. Whilst this still would have taken time to correct, it would not have taken as much time to correct compared to them all being written by hand (as such the decision could have been made later on).
Add Comment
Please, Sign In to add comment
