开发工具:Visual C++
上传日期:2001-02-11 01:46:14
上 传 者管理员
说明:  使用BorlandC++4.5编译的一个MUD客户端程序
( Uses a MUD customer end procedure which BorlandC 4.5 translates )

SRC (0, 1996-02-04)
SRC\ARRAY.C (5297, 1996-02-04)
SRC\BOBJ.C (4149, 1996-02-04)
SRC\CONFIG.H (585, 1996-02-04)
SRC\CONSOLE.C (5883, 1996-02-04)
SRC\CONST.C (2062, 1996-02-04)
SRC\DOC (0, 1996-02-04)
SRC\DOC\BUGS (1138, 1996-02-04)
SRC\DOC\RELEASE (1980, 1996-02-04)
SRC\EXTERN.H (8062, 1996-02-04)
SRC\FUNC.C (1910, 1996-02-04)
SRC\INTERP.C (14445, 1996-02-04)
SRC\KEY.C (2096, 1996-02-04)
SRC\KEYBOARD.C (5931, 1996-02-04)
SRC\MAIN.C (3541, 1996-02-04)
SRC\MAKEFILE (870, 1996-02-04)
SRC\OPER.C (7555, 1996-02-04)
SRC\PRMT.H (1921, 1996-02-04)
SRC\PRMT1.C (4218, 1996-02-04)
SRC\PRMT2.C (4389, 1996-02-04)
SRC\PRMT3.C (5077, 1996-02-04)
SRC\PRMT4.C (6907, 1996-02-04)
SRC\PRMT5.C (4416, 1996-02-04)
SRC\PRMTAB.C (8822, 1996-02-04)
SRC\RCS (0, 1996-02-04)
SRC\RCS\ARRAY.C (5643, 1996-02-04)
SRC\RCS\BOBJ.C (4485, 1996-02-04)
SRC\RCS\CONFIG.H (949, 1996-02-04)
SRC\RCS\CONSOLE.C (6239, 1996-02-04)
SRC\RCS\CONST.C (2386, 1996-02-04)
SRC\RCS\EXTERN.H (8410, 1996-02-04)
SRC\RCS\FUNC.C (2239, 1996-02-04)
SRC\RCS\INTERP.C (14782, 1996-02-04)
SRC\RCS\KEY.C (2432, 1996-02-04)
SRC\RCS\KEYBOARD.C (6273, 1996-02-04)
SRC\RCS\MAIN.C (3885, 1996-02-04)
SRC\RCS\MAKEFILE (1431, 1996-02-04)
SRC\RCS\OPER.C (7888, 1996-02-04)
SRC\RCS\PRMT.H (2265, 1996-02-04)
SRC\RCS\PRMT1.C (4560, 1996-02-04)
... ...

readme $Id: readme 2.1 1995/10/24 15:46:14 tsurace Release $ Installation ------------ VT should compile on SunOS, HP-UX, or a BSD-based system without changes. You can tweak the performance by going through config.h and commenting or uncommenting #defines for library functions you have. If you are uncertain about ANSI_CTYPES, compile and run test.c (cc test.c;a.out). It's probably also worthwhile to replcae the random number generator, since rand() is, although standard, not very good. If you do use standard Unix rand(), the following VTC function produces acceptable results: func rand(n) { return (n < 256) ? (rnd >> 7) % n : rnd % n; } To compile with hardcoded VT-102 terminal sequences instead of using the termcap library, replace -DTERMCAP with -DHARDCODE on the CFLAGS line of the makefile, and remove -ltermcap from the LIBS line. After you compile, you should probably strip the executable ('strip vt'). On an AIX system, compile with -DAIX. You will need to compile with -D_BSD and link with -lbsd, or use bsdcc. If you don't want to compile with -DHARDCODE, you will need to set up a termcap file. This involves finding someone with an /etc/termcap file on a BSD system, extracting the entry for your terminal type, placing it in your home directory, and setting: setenv TERMCAP ~/termcap setenv TERM vt100 These should be changed depending on where you put the termcap file and what your terminal type is. You can also include several entries in the termcap file and set TERM to the type of the terminal you are currently using, if you use multiple terminals. With BSD 4.3 Reno, compile with -DUSE_OLD_TTY. On a SysV system with BSD socket libraries, compile with -DSYSV and link with the socket libraries if necessary. Files ----- (This text is also in ../README.) You do not need to keep any of the files in src except for the vt executable. The executable can be placed wherever is convenient (e.g. ~/bin, /usr/local/bin). For a personal installation, you should leave the distribution files in ~/vt/dist and ~/vt/extra, as they are now if you untarred the archive in ~. You can also place them in ~ or ~/vt and VT will find them. For a system installation, you should put the files currently in the dist directory into /usr/local/lib/vt, and the files currently in the extra directory into /usr/local/lib/vt/extra. If this is not possible, edit the search path in main.c (in the src directory) to include the directory where you plan to place the dist files, and the search path in main.vtc (in the dist directory) to include the directory where you plan to place the extra files.