On Feb 6, 2004, at 7:36 PM, John M McIntosh wrote:
> Even as a 'to do' item is to document the VM to smalltalk interface 
> and ensure all popular VM do in fact match api and
> result expectations. A compliance document comes to mind, anyone 
> interested? All the source code should be accessible, all one
> needs to do is a lot of reading and consolidating the information into 
> some sort of readable document.
I've thought of this many times but (obviously) never got to it. I was 
considering a 'nullplatform' source tree with all the platform 
functions empty but heavily commented. Actually, some of the functions 
could have a fair bit of skeleton code as part of the explanation; for 
example the ioRelinquishProcessor code could have the lines relating to 
working out how long the delay might be to take into account any 
pending Delay etc. That's platform neutral and not necessarily obvious 
at first.

tim