So, I'm taking a MIPS course after returning to school; and we're approaching the point where we begin on our final project.
I've always been one for large, well-structured projects: lots of supporting tooling, well-segregated zones of control and concern within the project, extensive testing, so on and so forth. Unfortunately, I don't really know of much, or any, tooling for assembly-language code.
Hell, at the very most basic, I don't know how to compose multiple files (or to flip that on its head: how to decouple groups of procedures into files, and inter-reference amongst them.) Is there a standard(ish) practice for these things?
Barring other information, I'm suspecting I may have to use the C preprocessor (or
m4) :P to compose components; but besides that, how would you suggest I structure a larger project?
Also welcome: Any advice on writing relatively maintainable / shareable, clean, assembly-language code, beyond “use 8-space hard-tabs.”