aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--README.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/README.md b/README.md
index 496055d..493120b 100644
--- a/README.md
+++ b/README.md
@@ -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,