aboutsummaryrefslogtreecommitdiff
path: root/lib/inst.c
diff options
context:
space:
mode:
authorAryadev Chavali <aryadev@aryadevchavali.com>2023-11-01 17:49:33 +0000
committerAryadev Chavali <aryadev@aryadevchavali.com>2023-11-01 17:49:33 +0000
commit7a1129d80f6903db6e6a919bdeae403f924d69f6 (patch)
tree09410d90faae04bcd1aa4656e3d6b6bb9fee2118 /lib/inst.c
parent89fd2b0d17da72aec688946e89eeae4bf196e419 (diff)
downloadovm-7a1129d80f6903db6e6a919bdeae403f924d69f6.tar.gz
ovm-7a1129d80f6903db6e6a919bdeae403f924d69f6.tar.bz2
ovm-7a1129d80f6903db6e6a919bdeae403f924d69f6.zip
VM registers are now a dynamic array
Stack based machines generally need "variable space". This may be quite via a symbol-to-word association a list, a hashmap, or some other system. Here I decide to go for the simplest: extending the register system to a dynamic/infinite number of them. This means, in practice, that we may use a theoretically infinite number of indexed words, hwords and bytes to act as variable space. This means that the onus is on those who are targeting this virtual machine to create their own association system to create syntactic variables: all the machinery is technically installed within the VM, without the veneer that causes extra cruft.
Diffstat (limited to 'lib/inst.c')
0 files changed, 0 insertions, 0 deletions