oreodave/ovm
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added note in TODO.org

Browse Source 
Implementing start points has made features necessary for a standard
library setup easier to see.
This commit is contained in:
Aryadev Chavali
2023-11-03 21:23:26 +00:00
parent 232252c252
commit dea8e23807
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
todo.org
View File

@@ -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 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 the user has to specify in their source files?
Something to consider is /static/ and /dynamic/ "linking" i.e.: Something to consider is /static/ and /dynamic/ "linking" i.e.:
+ Static linking: assembler inserts all used library definitions into + Static linking: assembler inserts all used library definitions into
the bytecode output directly the bytecode output directly
+ We could insert all of it at the start of the bytecode file, and + We could insert all of it at the start of the bytecode file, and
with [[*Start points][Start points]] this won't interfere with with [[*Start points][Start points]] this won't interfere with
user code 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 + Furthermore library code will have fixed program addresses (always
at the start) so we'll know at start of assembler runtime where to at the start) so we'll know at start of assembler runtime where to
resolve standard library subroutine calls resolve standard library subroutine calls