From 94dbae25e521fc345d9a2c0f8c9beee90e29e16e Mon Sep 17 00:00:00 2001 From: Doni Pracner Date: Mon, 14 Apr 2014 18:18:35 +0200 Subject: [PATCH] more notes about what is different - heap, null, etc --- docs/mjc2wsl.txt | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/mjc2wsl.txt b/docs/mjc2wsl.txt index 27584dc..788e0bc 100644 --- a/docs/mjc2wsl.txt +++ b/docs/mjc2wsl.txt @@ -65,5 +65,15 @@ work. Note however that the language specification is not allowing direct access to the memory, neither is the bytecode actually working directly with the heap, and that array and object access are done by specialised commands. -Still there is an option for using indexes out of bounds -that could produce unexpected behaviour. \ No newline at end of file +Still there is an option for using fields beyond the actuall +object that could produce unexpected behaviour. +Array access in the MJVM does check for indexe out of bounds +errors. + +The size of the heap is not taken into consideration when +allocating new arrays and objects. What this means is that +there will be no heap overflow exception thrown, since our +heap is seemingly endless. + +Null access does not throw explicit errors, although it +will cause problems with the list access. \ No newline at end of file -- 2.25.1