Q: 3
Which file is a sequence of bytes organized into blocks understandable by the system’s linker?
Options
Discussion
Yeah, not A. The linker processes object files, not executables. Option C is correct here since object files contain the necessary blocks and symbol info. Executable (A) is a common trap because it sounds like the final product. Pretty sure C is right but let me know if there's another view.
Its C, since object files (.obj or .o) are what the linker actually reads and merges. Source files go to the compiler first, not straight to the linker. Seen this in practice labs too, but open to correction if I missed something.
Pretty sure it's C, not A. Executable is tempting but linker uses object files.
A is wrong, C. Had something like this in a mock and object file was the answer.
Option A. since executable files are laid out in blocks for the OS to run. I know C is what gets linked but the wording had me second guessing. Trap could be that both look structured for the system.
That’s C. Object files get linked, executables come later.
Had something like this in a mock and picked C. Object files have those organized blocks the linker needs, while executables come after linking. Pretty confident on this but could be missing something subtle.
Probably A, since the executable file is what gets used right after linking, and it's organized for the system. I get why C is popular but I think A fits too.
A tbh, executable file sounds closer since it's made of blocks for the OS, not just the linker.
A. I thought executable files were meant for the linker since they're ready to run, but now that I think about it, object files are what actually get passed to the linker for combining. Maybe someone can clarify if I'm off here?
Be respectful. No spam.
