Which feature of high-level languages most contributes to portability across computer systems?

Which feature of high-level languages most contributes to portability across computer systems?

• A. Abstraction from hardware
• B. Direct memory management
• C. Hardware-specific instructions
• D. Inline assembly blocks

Answer: (A)

Abstraction from hardware is what makes high-level languages portable. When a programmer writes in a high-level language, details about the computer’s processor, memory layout, and I/O devices are hidden. The language’s compiler or interpreter translates the same source code into the appropriate machine code for each target system, often using standard libraries and runtime environments to handle system-specific tasks. That separation means you can write code once and expect it to run on different computers and operating systems, as long as a compatible toolchain and libraries exist. Direct memory management tends to hurt portability because memory layout, allocation behaviors, and deallocation routines vary across platforms. Writing code that directly handles addresses or relies on specific memory models makes it harder to move to a different system without rewriting those parts. Hardware-specific instructions lock you into a particular CPU design. If code uses those instructions, it won’t run on other architectures without substantial changes. Inline assembly blocks are even more restrictive, embedding non-portable machine code inside high-level code and forcing a rewrite for other hardware or compilers.

Abstraction from hardware is what makes high-level languages portable. When a programmer writes in a high-level language, details about the computer’s processor, memory layout, and I/O devices are hidden. The language’s compiler or interpreter translates the same source code into the appropriate machine code for each target system, often using standard libraries and runtime environments to handle system-specific tasks. That separation means you can write code once and expect it to run on different computers and operating systems, as long as a compatible toolchain and libraries exist.

Direct memory management tends to hurt portability because memory layout, allocation behaviors, and deallocation routines vary across platforms. Writing code that directly handles addresses or relies on specific memory models makes it harder to move to a different system without rewriting those parts.

Hardware-specific instructions lock you into a particular CPU design. If code uses those instructions, it won’t run on other architectures without substantial changes.

Inline assembly blocks are even more restrictive, embedding non-portable machine code inside high-level code and forcing a rewrite for other hardware or compilers.