Author: chickendude
Posted: 27 Nov 2012 05:35:43 am (GMT -5)
1) Like willrandship said, you can simply send the shell to the emulator. WabbitEmu probably has a "save state" sort of feature that will load a savestate whenever you run it, that way you don't have to send the shell every time you want to test.
2a) Yep.
2b) Yep.
Include ion.inc in your program when a) you want to use the ion routines (in which case you'll also need to add the ion header) or b) you want to use the equates (i like to use the saferam equates). If you don't need either of those things you can just leave it out. If you get an error while compiling saying that something is undefined, then you might need to include ion.inc (or one of the other shell include files). The include files contain no actual code, including them won't make your program any larger or smaller, they simply provide equates so that you don't have to remember RAM locations, key codes, etc.
Posted: 27 Nov 2012 05:35:43 am (GMT -5)
1) Like willrandship said, you can simply send the shell to the emulator. WabbitEmu probably has a "save state" sort of feature that will load a savestate whenever you run it, that way you don't have to send the shell every time you want to test.
2a) Yep.
2b) Yep.
Include ion.inc in your program when a) you want to use the ion routines (in which case you'll also need to add the ion header) or b) you want to use the equates (i like to use the saferam equates). If you don't need either of those things you can just leave it out. If you get an error while compiling saying that something is undefined, then you might need to include ion.inc (or one of the other shell include files). The include files contain no actual code, including them won't make your program any larger or smaller, they simply provide equates so that you don't have to remember RAM locations, key codes, etc.