Subject: New Core

From: Andrew Wilson <[email-masked]>
Date: Sun, 25 Apr 1993 09:36:23 -0700

Mmmm, really, really great.  I guess NOW I'll have to start writing a
diff/patch system to work on different versions of the core.  Excellent, as is
I didn't have enough to do already.  There really HAS got to be a better
way of making changes to the core available without totally trashing stuff that
you've designed yourself.

Ignore me, I'm just mouthing off.

Maybe.

Net.

---

From: Mike Prudence <[email-masked]>
Date: Mon, 26 Apr 1993 00:50:46 -0700

Howdy all,

Andrew writes:

> Mmmm, really, really great.  I guess NOW I'll have to start writing
> a diff/patch system to work on different versions of the core.
> Excellent, as is I didn't have enough to do already.  There really
> HAS got to be a better way of making changes to the core available
> without totally trashing stuff that you've designed yourself.

As someone in the same boat, I've just taken the attitude that
LambdaCore is just an example of how to put things in a MOO, and not
necessarily the best way to do it, either.  Our core database (if you
can call it such) has a number of things that have a similar effect to
stuff that appears to be on Lambda, but done in different and arguably
better ways.

As 'core' upgradability was never part of the gameplan (excuse me if
I'm wrong, Pavel) I think we just have to forget about it.  Even if
you could upgrade your core, the amount of documentation on it is
nothing short of pitiful, especially if you want to do any serious
modifications or - God forbid - understand the *why* and *how* behind
such things.

As one of the authors of the LambdaCore documentation that can be
found on parcftp, I know what I'm talking about.  It also shows the
trend that those documents, which are still perfectly relevant to the
MOO I run, are now completely useless for the new LambdaCore.  Is
there no-one on Lambda who can be bothered to keep these up to date ?
More Kudos to Pavel for keeping the Lambda server documentation up to date.

There's more to MUDding than writing MOO code, I tell you.

> Ignore me, I'm just mouthing off.

Yeah, me too.  Still, count your blessings.  The whole problem could
have been avoided by not releasing the server code to us grunts so we
can run our own MOOs.

Cheers,

Mike/blip, the arch-documenter

[email-masked]                   "Only those who attempt the absurd will 
                                                     achieve the impossible."