I've never had to concern myself with linking, since one can specify what the externally contained include files are.

I normally generate and exercise my code modules separately and either invoke them as macros or simply paste them inline, which creates large but easy-to-follow code sets that are listed exactly as they're found in memory. I can include a macro library, which is where hardware drivers generally live, as macros depending on usage, and the assembler does the dirty work of adjusting the load addresses. Therefore the linking is handled internally by ASEM-51.

That's one of the more convenient features of this very handy tool. I can't see any use for a linker beyond handling pre-coded library contents. Aside from that, there's real advantage in having orderly sequencing of the modules in a piece of code, so that jumps and/or calls can be avoided when it's advantageous by properly ordering the various modules, thereby allowing code that otherwise would return only to call the same module on every execution to flow into that module. HLL's don't really make that convenient, or even predictable unless you totally integrate the modules. While it's possibly a distinction without a difference, it's easy to follow in ASM.

RE