62. The RTVMM of claim 1 wherein each object has a "lock" field initialized to a "null" value, the implementing step comprising the steps: causing a "hashlock object" for each object needing either a lock or a hash value to be allocated memory space and initialized, the "hashlock object" having a "hash value" field; causing the address of the "hashlock object" to be written into the "lock" field of the object; causing the hash value of an object to be retrieved by reading the "hash value" field of the associated "hashlock object".
62. The RTVMM of claim 1 wherein each object has a "lock" field initialized to a "null" value, the implementing step comprising the steps: causing a "hashlock object" for each object needing either a lock or a hash value to be allocated memory space and initialized, the "hashlock object" having a "hash value" field; causing the address of the "hashlock object" to be written into the "lock" field of the object; causing the hash value of an object to be retrieved by reading the "hash value" field of the associated "hashlock object". 64. The RTVMM of claim 62 wherein a monitor object is to be accessed and a "lock" field of the monitor does not have a "null" value thereby indicating the existence of a "hashlock object", the implementing step comprising the steps: causing a "count" field of the "hashlock object" to be incremented; causing a "u-owner" field of the "hashlock object" to be set to represent the current thread; causing access to be granted to the monitor object; provided the "count" field is 0 or the "u-owner" field refers to the currently-executing thread; otherwise: causing the currently-executing thread to be placed on a waiting list queue; causing the execution of the currently-executing thread to be blocked until access can be granted to the monitor object.