Timeline for How To Share Code Between Assembly Files In A Modular Way
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 6, 2024 at 15:50 | history | edited | CorkiMain | CC BY-SA 4.0 |
grammar
|
| Sep 5, 2024 at 20:52 | history | edited | CorkiMain | CC BY-SA 4.0 |
rewriting the question after amon explained some concepts I didn't understand
|
| Sep 5, 2024 at 15:48 | comment | added | CorkiMain | Thanks! I don't think I understand all of those concepts very well, but your comment helps. After reading your comment, my question is if there's a best practice for access control in assembly code? | |
| Sep 5, 2024 at 15:37 | comment | added | amon |
What you're encountering isn't assembly-specific, it's just how linkers work. The .global directive just marks a symbol as linkable, either exporting or importing it (compare extern in C, or the absence of a static qualifier). The .include doesn't work on a linker level, but on a textual level. You don't have header files in assembly because there are no types. The closest approximation would be to include a file that contains .global declarations, without defining those symbols. Header files in C aren't access control, they don't export functions from a translation unit.
|
|
| Sep 5, 2024 at 4:27 | review | Close votes | |||
| Sep 10, 2024 at 3:01 | |||||
| S Sep 4, 2024 at 21:46 | review | First questions | |||
| Sep 5, 2024 at 14:45 | |||||
| S Sep 4, 2024 at 21:46 | history | asked | CorkiMain | CC BY-SA 4.0 |