At 11:27 -0800 2001.04.15, Ned Konz wrote:

>Or you can just call Utilities>>timeStampForMethod: to get a timestamp.

Ah, thank you, thank you! Utilities>>timeStampForMethod: is just what 
I thought that I wanted.  (I never thought of looking in Utilities; I 
would tell my students that this should be a method on 
CompiledMethod.)

But thinking about this more, I don't actually need a timestamp; all 
I need to do is cache the old array of instVarNames and the old 
CompiledMethods in the model for my control panel, and compare 
(object identity) with the current ones.  This will be much faster 
than rummaging in the changes file for a timestamp!

I don't think that I can use the update/changed mechanism, because 
there are so many different ways in which methods and instance 
variables can be added to an object, including fileIn, the many 
different browsers, etc.  I think that I need to use the step 
mechanism to check on consistency every few seconds.

	Andrew