On Tue, Aug 17, 2010 at 06:24:40PM -0700, Eliot Miranda wrote:
BTW St?phane, IMO the VM's Slang code is far friendlier than the generated C. The Slang translator is the thing that's unfriendly. It doesn't do much verification and so when it mistranslates it can be hard to figure out what's going on. but the Slang/Smalltalk that implements the VM is fine.
Yes, and it is also much easier to read and understand the Slang/Smalltalk directly in the image.
It is also to be able to look at the C code, but you can do this directly in the image with SlangBrowser. In Pharo this is not integrated into the browsers (maybe someone can supply a patch for this?), but you can still display e.g. the generated C code for ObjectMemory>>fullGC from a workspace doit:
Transcript clear; show: (ObjectMemory asCString: #fullGC)
Or the fully inlined version as it would appear in the interp.c file:
Transcript clear; show: (ObjectMemory asInlinedCString: #fullGC)
Dave