From f02b1cba329b65763c27d1d9ccf80dfff805c2f1 Mon Sep 17 00:00:00 2001 From: Miquel Sabaté Solà Date: Mon, 10 Feb 2025 10:13:04 +0100 Subject: Add a note on debugging MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Miquel Sabaté Solà --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index d60f67f..d57385b 100644 --- a/README.md +++ b/README.md @@ -33,10 +33,10 @@ That being said, one good argument could be made that you could write the most performance critical bits in assembly and leave the business code in C so it's easier to understand or debug. That certainly is a possibility, but in the end the mixing of both languages can go wrong in different and hidden ways, makes -building and linking more complex, and, in my humble opinion, for not too much -to gain. Or at least that's how I feel, and programming in C might just be fine -for some people, but I prefer doing everything in assembly on NES/Famicom -development. +building, linking and debugging more complex, and, in my humble opinion, for not +too much to gain. Or at least that's how I feel, and programming in C might just +be fine for some people, but I prefer doing everything in assembly on +NES/Famicom development. That's why for the rest of this guide we will be talking about assembly and never about C or any other languages. -- cgit v1.2.3