diff options
| author | Miquel Sabaté Solà <mikisabate@gmail.com> | 2025-05-11 16:12:37 +0200 |
|---|---|---|
| committer | Miquel Sabaté Solà <mikisabate@gmail.com> | 2025-05-11 16:12:37 +0200 |
| commit | 4f0229934a4121eeabc14496ec3e9395d5af51f2 (patch) | |
| tree | 36d7458a877202a5756add94376d8a10cf2e38a3 | |
| parent | 9bfe160d8d54e3cdced46a34a92b12938dce229f (diff) | |
| download | style.nes-4f0229934a4121eeabc14496ec3e9395d5af51f2.tar.gz style.nes-4f0229934a4121eeabc14496ec3e9395d5af51f2.zip | |
Split a paragraph on the _x/_y convention
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
| -rw-r--r-- | README.md | 9 |
1 files changed, 4 insertions, 5 deletions
@@ -408,12 +408,11 @@ Reading from one controller or the other is the same but the `x` register can be used to select which controller to read. In general, this is a pattern in which the `x` or the `y` registers are used as a "select" for the function's code. This pattern can also be reproduced in functions that perform bank switching, -for example, as a way to index the bank to be selected. This can be further -documented by adding a suffix into the function's name, as it's done in the -above example. +for example, as a way to index the bank to be selected. -In this example, adding a suffix like `_x` is already telling the caller that -the `x` register is involved on this scenario. +This can be further documented by adding a suffix into the function's name, as +it's done in the above example. In this example, adding a suffix like `_x` is +already telling the caller that the `x` register is involved on this scenario. # Flow of control |
