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
..
.ethtest	Refactored state, state object and vm	2014-07-22 11:54:48 +02:00
address.go	Tests for native function calling	2014-10-14 13:37:26 +02:00
asm.go	Minor improvements and fixes to the new vm structure	2014-07-22 15:57:54 +02:00
closure.go	Couple of minor issues fixed	2014-10-15 00:40:41 +02:00
common.go	Fixed remote Arithmetic tests	2014-10-15 17:12:26 +02:00
debugger.go	Refactored VM to two separate VMs; std & debug	2014-10-14 11:48:52 +02:00
environment.go	Couple of minor issues fixed	2014-10-15 00:40:41 +02:00
execution.go	Couple of minor issues fixed	2014-10-15 00:40:41 +02:00
stack.go	VM execution fixes	2014-09-15 22:11:05 +02:00
types.go	Refactored VM to two separate VMs; std & debug	2014-10-14 11:48:52 +02:00
virtual_machine.go	Tests for native function calling	2014-10-14 13:37:26 +02:00
vm_debug.go	Use the state instead of the state object directly.	2014-10-16 13:38:21 +02:00
vm_test.go	Removed old installer script	2014-10-14 15:31:25 +02:00
vm.go	Fixed remote Arithmetic tests	2014-10-15 17:12:26 +02:00