Compile-and-Go loading schemes — drawbacks: Which of the following describes the disadvantages of a classic Compile and Go loading scheme in program development?

Introduction / Context:
Early development environments often used Compile and Go schemes, where the assembler or compiler immediately produced in memory code and transferred control to it. While simple, this approach has notable drawbacks for larger or modular systems.

Given Data / Assumptions:

• Assembler or compiler remains resident during translation.
• No separate loader or linker phases are used.
• Programs may be multi module and multi language.

Concept / Approach:

Since the translator occupies memory, less RAM is available for the object program, leading to waste. Without a separate object file and loader, the source must be retranslated each run, increasing time. Finally, modular and mixed language builds are hard without a proper link step, limiting maintainability.

Step-by-Step Solution:

Verification / Alternative check:

Modern toolchains separated compile, assemble, link, and load stages precisely to resolve these disadvantages, validating the analysis.

Why Other Options Are Wrong:

• Each individual disadvantage is true, so selecting only one is incomplete.
• None of the above contradicts well known limitations of Compile and Go.

Common Pitfalls:

Assuming simplicity translates to efficiency at scale; not accounting for iterative development where recompilation costs add up.

Final Answer:

all of the above