[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

3405: Re: [MUD-Dev] MUD Design Fundamentals (Was: Looking for

[Full Header] [Plain Text]
From: "Jon A. Lambert" <jlsysinc@ix.netcom.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Sun, 31 Aug 1997 15:56:35 -4
References: [1]
Organization: Kanga.Nu
On 30 Aug 97 at 21:48, Ola Fosheim Grostad wrote:
> 
> Well, I agree, that the ideal situation would be to have persitance as a
> part of the language design specs.  I still don't see how you can ignore
> realtime information, UNLESS the language is dedicated to the task at hand.

This would describe ColdC and some others' systems on the list to the 
best of my knowledge.  

> My main point was that persistance isn't neccessarily going to save your
> butt, although it "sounds like magic".  I would at least go for secondary
> backup functions that store information in an easily parsable format for
> saving and loading the most essential information.  If not, you are
> probably stuck with your initial design, or have to accept more clean
> wipes than you like.
> 

I'd be interested in how you apply the concept of "dynamic evolution" 
in mud worlds without some notion or application of persistence.  I 
see them as being quite linked.  

Jon A. Lambert