Re: CRC

• Date: Wed, 14 Feb 1996 12:24:24 PST
• From:
  Kipp the Kidd <mcmudge@mailbox.syr.edu>
• Content-Type: text/plain; charset="us-ascii"

>But the big problem, especially on objects that are maintained by a group,
or in 
>the case of most of my objects where the users can expand the object
themselves, 
>what do you do in the case where more than one version of an object on
different 
>MOOs have been updated within a checking period?  Would it be possible to 
>include some code here for merging differences in props to both?  And what of 
>verb code that *has* to be different on different MOOs due to core
differences?  
>The different ways integration is handled comes to mind...  Can we put in 
>machine-readable comments around blocks that need not be included in the 
>checksum, and aren't replaced in updates?

My core is very organized.  The only object that won't be updated is #1, the
archwizard.  $local has many, many options about how the MOO should run (and
therefore is NOT destroyed in a make_core_database) so verbs and properties
are only ADDED if they don't exist.  If they do exist, the updater assumes
that the verbs and props are set to the archwizard's tastes, and therefore
leaves them alone.  For the rest of the objects, verb code is updated, and
props are added.

- Kipp
-----BEGIN GEEK CODE BLOCK-----
GCS/CC d- s+:- a16 C++ UL++++ P+ L++ E-? W+ !N--@ !o-- K->K++++++
w++(--) O- M-- V--? PS++(+) PE(--) Y+ PGP-? t+ 5(+) X++ R+++(*)
!tv b+ DI++++ D++++ G e* h!()(*) r+ !y+
------END GEEK CODE BLOCK------
-----BEGIN NOT SO GEEKY BLOCK-----
MOO projects:
  RPG Minimal.db:  paradigm.microwave.com 5000
  MOO2000:         moo.microwave.com 2000
  MundoHispano:    europa.syr.edu 8888
------END NOT SO GEEKY BLOCK------

• Prev: Re: CRC
• Next: Critical Patch #2 for LambdaMOO release 1.8.0beta1
• Index: MOO-cows
• Thread: MOO-cows