Subject: Re: Bug in read() and release 1.7.0

From: [email-masked] (Michael Richardson)
Date: Wed, 2 Sep 1992 20:20:03 -0700

On Sep 2,  6:50pm, Pavel Curtis wrote:
} next speed bottleneck in line.  Also, the notion of `clear' property values,
} through which you can see the value of that property in the parent, is now
} implemented and working.  This latter feature should allow for a major space
} savings, since child objects whose properties haven't been changed since
} creation have all their properties clear, so that they don't duplicate the
} values in the parent.  We're going to apply this notion to LambdaMOO's DB
} retroactively today or tomorrow and we're expecting a major drop in

  I think the most important aspect of this from the MOO programmer's
point of view is that properties could now `copy-on-write'. There was
a bunch of non-MUD things I was doing with MOO (1.2 I think) last year
that was really begging for `copy-on-write'
  I assume that it is possible to restore the `clear' state to a
property?

-- 
   :!mcr!:            |  The postmaster never | So much mail, 
   Michael Richardson |    resolves twice.    |  so little time.
HOME: [email-masked]     Bell: (613) 237-5629
SCHOOL: [email-masked]

---

From: Pavel Curtis <[email-masked]>
Date: Thu, 3 Sep 1992 11:44:05 -0700

> Date:	Wed, 2 Sep 1992 20:20:03 -0700
> From:	[email-masked] (Michael Richardson)
> 

Yes, with the new `clear_property(obj, name)' built-in function.  Also, you can
test for `clarity' with the new `is_clear_property(obj, name)' built-in
function.

	Pavel