Commit Graph

5 Commits

Author SHA1 Message Date
obscuren 70f7a0be11 Use the state instead of the state object directly.
If a state gets reset and you still hold a pointer to the previous,
incorrect, state object you'll operate on the wrong object. Using the
state to set/get objects and attributes you won't have this problem
since the state will always have the correct object.
2014-10-16 13:38:21 +02:00
obscuren 311c6f8a3f Fixed remote Arithmetic tests 2014-10-15 17:12:26 +02:00
obscuren 3d177be73e Couple of minor issues fixed
* CALLVALUE pushed incorrect value to the stack
* Set execution model to closure
2014-10-15 00:40:41 +02:00
obscuren f55e39cf1a Tests for native function calling 2014-10-14 13:37:26 +02:00
obscuren c5bd32b0ad Refactored VM to two separate VMs; std & debug
Standard VM should be about 10x faster than the debug VM. Some error
checking has been removed, all of the log statements and therefor quite
some unnecessary if-statements.
2014-10-14 11:48:52 +02:00