I've been using ca65 for development and employ a fair amount of macros. I prefer them mainly for abstraction and code readability so that a single descriptive macro can be used in place of several lines of asm. Less is more. Sometimes this is counterintuitive though, especially when revisting an older project and the macros might provide more confusion than clarity (I guess that's true for any code though, functions etc). Anyone have thoughts, or a doc, on judicial use of macros? What's overboard, when should the code stay inline, or move into a function instead, etc.
Statistics: Posted by gzip — Fri Dec 20, 2024 11:47 am — Replies 3 — Views 228