diff options
| author | Miquel Sabaté Solà <mssola@mssola.com> | 2026-09-15 17:09:33 +0200 |
|---|---|---|
| committer | Miquel Sabaté Solà <mssola@mssola.com> | 2026-09-15 17:09:33 +0200 |
| commit | 86fe8c9f1a629e9bb6646ef42ef13d5a713d72f8 (patch) | |
| tree | 8109afc0330e22af7da4e3b2a8b8a91ddb3e1066 | |
| parent | 3cd175e16fd4053ef1c1c27a0ff6e017e40c558c (diff) | |
| download | style.nes-main.tar.gz style.nes-main.zip | |
Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>
| -rw-r--r-- | README.md | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -445,8 +445,11 @@ kind of scoping could be useful if performance was paramount. That is, imagine a movement. This could be done in multiple ways, but the most performant way would be to just `jmp (pointer)`, and then let each handler perform a `jmp @known_return_address` instead of a mere `rts`. Hence, if you are on corner -cases like these, I think it's fair to go the optimal route. In other cases, -prefer readability. +cases like these, I think it's fair to go the optimal route. As a last touch, +`nasm` also allows developers to use [global +labels](https://git.mssola.com/nes/tools.nes/about/crates/nasm/README.md#defining-global-labels). You +can also use that for corner cases. In any case, and when in doubt, prefer +readability. Moreover, note that tooling might perform better if the programmer states explicitely that this is indeed a subroutine and not a mere label. This way, |
