NOTE: Read the "Known Bugs" section at the end of file!

Requirements:

A standard C++ compiler with fairly up-to-date template support.
A flavor of UNIX that supports Berkeley sockets.

If your OS doesn't have a C++ compiler (probable) then get the
GNU C/C++ compiler from prep.ai.mit.edu /pub/gnu/gcc-X.X.X.tar.gz
and build it for your machine. If you can't get the compiler built
then a cheap option is to either get a Linux or FreeBSD distribution
and run your game on an Intel platform. Hint: Linux rules.

I used gcc 2.6.0, 2.6.3, 2.7.0, 2.7.1 and 2.7.2 in the development of MUD++.
Versions earlier than 2.6.0 (2.5.8 for example) had problems with the
way I instantiated templates. I am confident that you will need at least
2.6.0 to compile and run mud++ successfully. The most problematic area
that you may run into is templates, nested templates and exceptions. The
best bet is to upgrade to at least 2.6.0 or get your sysadmin to do it for
you. Please don't mail me saying, "I'm using gcc 1.x.x and it doesn't
support inlining" or some garbage. My response will be, C++ is standard
enough now, upgrade your compiler to a decent version or go run a
standard C MUD server.

I have successfully compiled and run MUD++ on the following platforms
firsthand, although some of the tests were done at different times so
if one of these platforms gives you problems, mail me specifics.

o Linux 1.1.x, 1.2.x, 1.3.x
o DEC ULTRIX 4.2BSD, 4.3BSD ( ULTRIX mmap() seems broken )
o DEC Alpha UNIX/OSF 3.2C
o Solaris/sparc 2.4 - thanks to Mech Maniac for the machine.
  Solaris/x86   2.5 - I paid for it. :P
o BSDI (version ???)

As of 0.5 the C++ source is compatible with the following compilers.

o GNU C/C++ 2.6.0 - 2.7.2
o Solaris Proworks C/C++ 4.0

Ports underway

o Win32 - The port to the Win95/NT platforms is being done by
  John Olson (jwo@netcom2.netcom.com)

Testing info on other compilers/platforms is welcome.

---
Known Bugs 

o Linux 1.2.13 with some version of libc barfs when new player
  connects due to gethostbyaddr() bug. Comment that out and set
  to NULL to run. I personally ran it on 1.2.13 with no problem
  so it is surely in libc.

o File descriptor leak where process eventually has too many open
  descriptors due to not closing something.