MUD++ pre-release Alpha

Copyright(C) 1995 Melvin Smith - Mercer University, Macon GA. MUD++ is in no way related or derived from any other existing mud, mush moo, muck, chat, etc. MUD++ stands for Multi User Dimension. The ++ is because the whole shebang is coded in C++ using OOP. What MUD++ has that you probably wont find in another base code.

Distributed server (run your mud on multiple hosts)
Coded in C++ using OOP methods. Easier to extend.
IO class that does not use stdc++ so you don't need GNU's libg++
Buffered OutFile class with user defined cache size.
Memory mapped InFile class for very fast reads/parses.
Online Creation/Editing
Selective area reloading.
Repops are encapsulated in each room. Not 1 big list.
Helps are offline text files. Saves memory in long run and allows -very- large help files and easy management.
An object oriented TCP/IP server that can be used in another application without modifications. (server.h and server.cc)
OOP Socket class. Borrow it for your own code.
String class - memory sharing, copy on write. Takes care of allocations and resizing itself.
Linked List class - Allows easy traversal, inserts and removals.
Unlimited bit system and bit based security for imm commands.
Scope based index system instead of the standard Vnums.
Color ( preliminary )
Nice spell parser. The holy symbol ' is not needed.
Object types and spell names are stored in the string form allowing areas to be passed between servers with different spells, types.
Hot reboot that doesn't close connections.
Ident support. (blocks right now)
Environment that affects players (in early stages)
ONLY 1 COPYRIGHT!!

Future releases:

Languages.
Distributed MUD Server improvements.
Online compiled language for triggers, scripts, spells.
MUD processes ( multi-tasking )
Certain SQL front end extensions.
X client, Windows client.
Windows based remote server manager.
MUD Mail/Email ( already written, but incomplete )
SMTP email back end for forwarding MUD mail. ( incomplete )

What probably -wont- be in Future releases and why.

Explicit multi-classing. I have never seen two imps agree on a multi class system and I have decided that multi-classing is out of scope of a base code. Instead the base will incorporate a system of its own and be designed in a way that any imp can add multi-classing with minimal work.
Support for Diku, Merc, Envy, ROM, Circle area files. If enough people want something, someone will usually write it and post it to the list.