diff options
| author | Aryadev Chavali <aryadev@aryadevchavali.com> | 2023-11-03 21:23:26 +0000 |
|---|---|---|
| committer | Aryadev Chavali <aryadev@aryadevchavali.com> | 2023-11-03 21:23:26 +0000 |
| commit | dea8e238074291c181f6780e445d046d08ca6668 (patch) | |
| tree | 1629a1b3a7f8854c6dff8f3060798a13f6f672dc /todo.org | |
| parent | 232252c2521d87f4148942a5154167be948183bb (diff) | |
| download | ovm-dea8e238074291c181f6780e445d046d08ca6668.tar.gz ovm-dea8e238074291c181f6780e445d046d08ca6668.tar.bz2 ovm-dea8e238074291c181f6780e445d046d08ca6668.zip | |
Added note in TODO.org
Implementing start points has made features necessary for a standard
library setup easier to see.
Diffstat (limited to 'todo.org')
| -rw-r--r-- | todo.org | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -7,12 +7,16 @@ I should start considering this and how a user may use it. Should it be an option in the VM and/or assembler binaries (i.e. a flag) or something the user has to specify in their source files? + Something to consider is /static/ and /dynamic/ "linking" i.e.: + Static linking: assembler inserts all used library definitions into the bytecode output directly + We could insert all of it at the start of the bytecode file, and with [[*Start points][Start points]] this won't interfere with user code + + 2023-11-03: Finishing the Start point feature has made these + features more tenable. A program header which is compiled and + interpreted in bytecode works wonders. + Furthermore library code will have fixed program addresses (always at the start) so we'll know at start of assembler runtime where to resolve standard library subroutine calls |