8 Apr
2013
8 Apr
'13
2:33 a.m.
On 2013-04-07 5:00 AM, Frank Shearar wrote:
(*) I'll ignore the obvious problems of side effects: deleting things on the file system, launching missiles and the like. In Smalltalk that's a very, very big problem to solve (because of how baked in side effects are in the standard libraries, and the code built on the standard libraries), and we don't have an type/effect system to help us identify same.
Virtualizing the primitives (adapting standard CPU virtualization tricks to the Smalltalk VM) might suffice (and would permit a bunch of other really interesting stuff at the same time). Hmm, though enforcing no-shared-memory might be a bit challenging.
Tony