Hello all,
I liked until now how the separation between platform and game related code was done, with the game being basically a service to the platform.
Until day 14, the game layer had no knowledge of the platform layer, but, with file I/O in the latest video, now the game is calling directly functions defined in the platform layer, kind of breaking the model.
Is this "exception" going to remain in the final versions of the file I/O functions as well ?
Is there a way to get around it (function pointers ?) ?
(and, that you know, is it possible to ask Casey questions "asynchronously", for those of us that cannot follow the live Q&A (email ? will he read the forums ?) ?)
I liked until now how the separation between platform and game related code was done, with the game being basically a service to the platform.
Until day 14, the game layer had no knowledge of the platform layer, but, with file I/O in the latest video, now the game is calling directly functions defined in the platform layer, kind of breaking the model.
Is this "exception" going to remain in the final versions of the file I/O functions as well ?
Is there a way to get around it (function pointers ?) ?
(and, that you know, is it possible to ask Casey questions "asynchronously", for those of us that cannot follow the live Q&A (email ? will he read the forums ?) ?)
Yes, he reads the forums. See here: https://forums.handmadehero.org/i...orum/profile?view=user&userid=431
And Casey repeated multiple times in last video that this file i/o is only for debugging purposes (that's why DEBUG prefix). Real i/o will done later differently.
And Casey repeated multiple times in last video that this file i/o is only for debugging purposes (that's why DEBUG prefix). Real i/o will done later differently.