[DGD] Question...

[Noah Gibbs]

  I store rooms, portables and helpfiles in large files with large numbers
of entries -- I used to store one help entry per file, and it starts to
suck pretty quickly.  The problem with storing one room, portable or
(gag) exit per file is the sheer number of files that build up.
  But then, I don't use save_object() -- I use an XML-like structured
storage language called UNQ with XML-like DTDs.  And it means that certain
kinds of bugs *are* just tough to track down.  I may start having to use
explode() to cut the file up into sections before doing my current
parse_string parsing -- otherwise when a file isn't parsed as valid UNQ
parse_string will just return nil and I have no idea where the error is.
  But for bugs after parsing has occurred, I just have a lot of error
checking code so if there's a bug I know what entry it's in -- I make sure
my error message tells me.  And when doing the DTD structured parsing
after the parse_string pass I actually keep a separate parser_error stack
of error messages so I can find out exactly what the problem is, and in
what entry.  It's a lot of error check code, but I wrote it once and now I
use it almost everywhere.

-- 
angelbob at monkeyspeak.com
See my page of DGD documentation at
"http://www.angelbob.com/projects/DGD_Page.html"
If you post to the DGD list, you may see yourself there!

On Wed, 27 Feb 2002, Sergey S. Koval wrote:

> Hello,
> 
> Tuesday, February 26, 2002, 1:18:13 PM, you wrote:
> 
> VIL> Hello Sergey,
> 
> VIL> I would say this is not the way of creating rooms and NPCs :)
> VIL> If something bugs, it will be a pain in the ass to find the bug.
> VIL> But that's only my opinion.
> Hmmm, not really :-)
> Is there is somewhere bug, i know that it is somewhere in
> room object. If something goes wrong, all i have is
> just to look at one file and try to find a bug.
> 
>  Actually, i'm using LPC as a programming language, but
> i don't like some common LPC concepts, like creating
> every room in different file, etc. What about security ?
> All coders in my MUD are people that i know in real life.
> I can trust them. They know what they can do and
> what they shouldn't. About world builders - they
> have own commands and have no access to LPC code.
>  In such enviroment, one file for world is much
> more preferred than bunch of tiny LPC files.
> I know that DGD can swap out all objects to disk
> and later restore it. But what happens with connected
> players (at moment of world save) ?
> 
> Also, what about containers ? I started coding in LPC
> with MudOS driver. I have some experience of coding
> in Diku muds (Anatolia - ROM deriviative), that's
> why i'm trying to get best from it into my own MUD.
> In MudOS i stucked with container problem. Solution
> is simple - just create subdirectory and store
> objects in container in this directory.. But what
> about cleaning directory structure ? One error and
> i can wipe recursively all player/world/etc (unprotected
> ) data. Is there in DGD some better solution ?
> 
> P.S. I'm still deciding move to DGD (it means, start
> from scratch) or continue using MudOS (looks like
> MudOS is trying to raise from it's knees, but i don't
> trust MudOS anymore).
> 
> Regards, Serge.
> ----------------------------------------------
> Save time... see it my way.
> ----------------------------------------------
> 
> _________________________________________________________________
> List config page:  http://list.imaginary.com/mailman/listinfo/dgd
> 

_________________________________________________________________
List config page:  http://list.imaginary.com/mailman/listinfo/dgd