Subject: managing libraries

From: [email-masked]
Date: Wed, 22 Sep 1993 09:55:11 -0700

How do you folks edit and manage large libraries like $XXX_utils?

We're trying to do source code control here, as well as make objects
portable from database to database, and are writing verbs to dump out and
restore objects with their properties and verbs, but I was wondering what
y'all did.

While I'm on the topic.

The psuedo-properties such as .programmer:

If you wanted to be sure that an object from one database behaved properly
in another, would it be necessary to save/restore these?

If so, where would one find a complete list of these things?

Are they in source code, or extensible?
-- 
--
-- "TANSTAAFL" Rich [email-masked]

---

From: Judy Anderson <[email-masked]>
Date: Wed, 22 Sep 1993 10:37:21 -0700

Uh, we just up/download the appropriate definitions to/from our client
and sometimes remember to tell *core that we did it.  On OpalMOO their
@maogram maintains a time stamp in the verb code itself (this is a
good idea, maybe LMoo should do it).  I use @dump to port things to
other moos, this always entails a bit of editing of the @dump script
but it hasn't bothered me enough to figure out the real hard thing of
actually getting a script creator that is bulletproof.  (Well, #404 on
LMoo is pretty bulletproof, but its output is hard to read.)

$code_utils.buildin_props has a list of built in properties.  It must
be maintained by hand if you add a builtin to the server.