From 4f0229934a4121eeabc14496ec3e9395d5af51f2 Mon Sep 17 00:00:00 2001 From: Miquel Sabaté Solà Date: Sun, 11 May 2025 16:12:37 +0200 Subject: Split a paragraph on the _x/_y convention MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Miquel Sabaté Solà --- README.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index a19595a..53b07d1 100644 --- a/README.md +++ b/README.md @@ -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 -- cgit v1.2.3