From: Doni Pracner <quinnuendo@gmail.com>
Date: Mon, 14 Apr 2014 16:18:35 +0000 (+0200)
Subject: more notes about what is different - heap, null, etc
X-Git-Tag: v0.1.6~7^2~4
X-Git-Url: http://svarog.pmf.uns.ac.rs/gitweb/?p=mjc2wsl.git;a=commitdiff_plain;h=94dbae25e521fc345d9a2c0f8c9beee90e29e16e;hp=13d9b6940ed9c98556e7d2af0ceb9757ce3dc68e

more notes about what is different - heap, null, etc
---

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