[MUD-Dev] Re: An Introduction

[Ross Nicoll]

>> Layers, yes, but also lots of fairly independent modules. E.g. in my
>> server, the database code is separate, the lexer for the programming
>> language is separate, the parser is separate, the interpreter is
>> separate, the socket stuff is most separate, etc. etc. I tend to think
>> in boxes rather than in layers, although the stuff written in the MUD
>> programming language is definitely layered on top of the server itself.
>Do you find your codebase faster than most stock code? Or easier to code upon?
As someone with some experience playing with his server, I find the code
very fast (I was amazed when I discovered it wasn't compiled into an
internal machine code).

I actually got bored one day and tried porting my entire MUD server's
commands/skills/everything to the server... it is generally quite easy
to code for, and given time what I was trying would be possible, but
syntax gives me a few problems (it's closer to Maple, which is all I
have experience with that's similar).

The other really serious problem I have with it is it is quite difficult
to change code once it's in the system, and that you really need to
keep an external copy of all the text needed to set up the DB, which
takes a while for the server to take in once you get to anything
really usable.

Hey, Chris is you're readin this, how about having the server be able
to dump the DB into a source file? Would be ugly I know, but might be
a nice option...

  _   __  __  __         Ross "Xugumad" Nicoll
 /_) / / (_  (__
/\  /_/  __)   /
______________/