mirror of https://github.com/nmlgc/ReC98.git
0dcd0b8136
`cPtrSize` is simply the wrong constant for calculating parameter offsets on the stack, because it corresponds to the memory model's default distance, not the function's distance. Luckily, ARG has a RETURNS clause, and if you declare all parameters in there, ARG won't emit that pesky and unnecessary `ENTER 0, 0` instruction. Big discovery right there! Sadly, ARG is unusable for ZUN's silly functions that keep the base pointer in BX. TASM declares the resulting equates as `[BP+offset]`, and it's apparently impossible to only get `offset` out of such an equate later. So, rather than staying with numbers, let's reimplement ARG for these functions instead. This way, we can even abstract away the stack clear size for the `RET` instructions. It's a bit rough around the edges though, forcing you to explicitly specify the function distance, and to pass the parameters in reverse order compared to the C declaration (thankfully, all of these use the PASCAL calling convention). It also doesn't work with more complex types yet. But certainly better than numbers. Part of P0134, funded by [Anonymous]. |
||
|---|---|---|
| .. | ||
| bomb.hpp | ||
| bomb[bss].asm | ||
| bombanim.cpp | ||
| bombanim[bss].asm | ||
| invalidate.asm | ||
| move.asm | ||
| option[bss].asm | ||
| player.h | ||
| player.inc | ||
| pos[bss].asm | ||
| pos_update_and_clamp.asm | ||
| render.asm | ||
| shot.hpp | ||
| shot_laser.asm | ||
| shot_laser[data].asm | ||
| shot_levels[data].asm | ||
| shot_velocity.asm | ||
| shot_velocity[data].asm | ||
| shots[bss].asm | ||
| shots_add.asm | ||
| shots_add[bss].asm | ||
| shots_alive[bss].asm | ||