Assemblers and immediate execution Which system program skips producing an object file, generates absolute machine code, loads it, and executes immediately after assembly?

Introduction / Context:
Development workflows can assemble code to an object file for later linking, or assemble and execute immediately for rapid testing. Load and go assemblers streamline short edit assemble run cycles, especially in educational and embedded contexts.

Given Data / Assumptions:

• We compare standard assemblers with a variant that loads and runs immediately.
• Object code and absolute code are different products.
• Immediate execution implies an integrated load step.

Concept / Approach:

A load and go assembler translates source to memory resident absolute code and jumps to it without writing an intermediate object module. A two pass assembler typically emits relocatable object modules for a linker. Macroprocessors expand macros but do not assemble or execute. Compilers translate high level languages into object or executable files, not immediate execution of assembled code.

Step-by-Step Solution:

Verification / Alternative check:

Historical educational systems and monitors provided load and go assemblers for quick turn programming, confirming the definition.

Why Other Options Are Wrong:

a: two pass assemblers typically output relocatable objects. c: macroprocessors perform text substitution only. d: compilers translate high level code and usually require linking.

Common Pitfalls:

Confusing a monitor or debugger with an assembler; assuming all assemblers require linking steps.

Final Answer:

Load-and-go assembler.