About the emulator/virtual calc discussion, virtual calcs are somewhat problematic thanks to the archive issues, but Omnicalc's RAM recovery option works fairly well for testing assembly programs. It could be better, obviously, but the feature has certainly saved me a lot of time over the years, for those times when an emulator isn't good enough and you have to test on the real hardware.
I myself definitely find jq useful. The only things the assembler is missing IMO are macros, true defines, the ability to move and rename (including changing the section type) sections, and the include directive. Then it'd be awesome 
Moving and renaming sections is a good idea. I'll see what I can do. Macros will be done at some point, but those are a bit tricky.
INCLUDE would actually be quite a bit more difficult. I realize it's nice to have for porting existing code, but is there a reason you really need it?
FloppusMaximus, could you better specify how library source files are included (with respect to the order in which they are assembled into the source, that is)?
I believe that they're assembled in the order they're listed, by a breadth-first search (so the main source file comes first, then all the files imported by the main source file, then all the files imported by those files (assuming they weren't used already), and so forth.) So if you want the files in a particular order, just be sure to list all of them in the main source file.
If you're writing a general-purpose library that depends on other libraries, you can't predict what order those dependent libraries will appear, but the section types do allow you to define a partial ordering of
sections (all header sections come before all code sections, which come before all data sections, which come before all footer sections.)
Show Posts