diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -7,9 +7,9 @@ to be enforced. That is, it's just a set of ideas I try to follow in order to be consistent mainly with myself. Hence, it's not complete and I can still be persuaded away from things I say here. All in all, take all of this with a grain of salt and assume that if I write something that looks fishy, maybe it's just -that I don't know any better and I might be able to be convinced via a [Github -issue](https://github.com/mssola/style.nes/issues). That is to say, discussions -are welcome, even if I can always just say no. +that I don't know any better. If that's the case, then just drop me an +email. That is to say, discussions are welcome, even if I can always just say +no. Last but not least: get to know the NES/Famicom first! This is not a reference guide nor a list of pitfalls that should be avoided. For all of this, just refer @@ -240,7 +240,7 @@ But it also has its drawbacks: All of that being said, the first benefit that we pointed out is not to be overlooked, but it can arguably be achieved via tooling as well. That's what I'm doing with the "address sanitizer" in -[mssola/tools.nes](https://github.com/mssola/tools.nes). +[tools.nes](https://git.mssola.com/nes/tools.nes). # Naming conventions @@ -266,10 +266,10 @@ lda #01 ; good! One good idea for `.macro` is to use them to define pseudo-instructions, as it's done in other assembly languages like RISC-V. For example, on [these scrolling -examples](https://github.com/mssola/code.nes/tree/main/scroll) there is a macro -for the pseudo-instruction `JAL`, which makes explicit when a `jmp` has been -used instead of `jsr` for reducing the stack usage on tail calls. In this -scenario, you can find code like this: +examples](https://git.mssola.com/nes/code.nes/tree/scroll) there is a macro for +the pseudo-instruction `JAL`, which makes explicit when a `jmp` has been used +instead of `jsr` for reducing the stack usage on tail calls. In this scenario, +you can find code like this: ```assembly .proc foo |