Assembler variants: which system program skips writing a separate object file and instead generates absolute machine code directly in memory, loading it into main storage so execution can start immediately after assembly?

Introduction / Context:
Assembly toolchains vary in how they deliver executable code. Traditional assemblers emit object modules for later linking, while specialized workflows shorten the cycle for rapid testing or educational use by loading code directly into memory for immediate execution.

Given Data / Assumptions:

• Goal: execute the assembled program right away without a separate link/load step.
• Memory image is written directly to the execution location.
• Absolute addresses are used or resolved during assembly.

Concept / Approach:
A load-and-go assembler combines assembly with direct loading. It forgoes producing an object file and emits executable bytes directly into designated memory, then transfers control to the entry point. This accelerates turnaround but sacrifices modular linking flexibility.

Step-by-Step Solution:

Verification / Alternative check:
Historical educational assemblers and monitor programs on early microcomputers exemplify load-and-go behavior: assemble, then run—no object file persists.

Why Other Options Are Wrong:

Common Pitfalls:
Assuming all assemblers produce object files; overlooking environments that privilege immediacy over modularity.

Final Answer:
load-and-go assembler.