Croquet VM issues

[David T. Lewis]

On Fri, Mar 17, 2006 at 11:07:31AM +0100, Bert Freudenberg wrote:
> Am 17.03.2006 um 05:35 schrieb Andreas Raab:
> > It's not for security. It's really so that we know whether a VM has  
> > ever been put to the test or not. In other words when the image  
> > starts, it would check whether it has been started with an  
> > "unknown" VM and if so, runs its VM tests and reports to the user  
> > if there are any issues. The thing is that some of these tests take  
> > some time and rather than running them anew upon each start of the  
> > image I'd like to be able to checksum the VM and run them only when  
> > we detect that the VM has changed.
> 
> Right. So if a user chooses some non-canonical way to run the VM that  
> screws up system attribute 0, he just will have to wait longer.
> 
> OTOH, if you're building a new VM anyways using the new math lib,  
> what's the problem with adding a primitive for checking? There are  

Yes, having the VM identify itself through a primitive sounds like a
simpler and more reliable approach.

Dave