文件列表:

source32\1\LIFE\LIFE.CPP (3103, 1999-09-29)
source32\1\LIFE\LIFE.H (286, 1999-09-29)
source32\1\LIFE\MAIN.CPP (849, 1999-09-29)
source32\1\LIFE\MAIN.EXE (44742, 2000-06-01)
source32\1\LIFE\UTILITY.H (298, 1999-09-29)
source32\1\LIFE\UTILITY.CPP (521, 1999-09-29)
source32\1\LIFE (0, 2006-03-02)
source32\1 (0, 2006-03-02)
source32\10\AVLT\ANODE.CPP (11915, 1999-09-29)
source32\10\AVLT\ANODE.H (325, 1999-09-29)
source32\10\AVLT\ATREE.CPP (993, 1999-09-29)
source32\10\AVLT\ATREE.H (793, 1999-09-29)
source32\10\AVLT\MAIN.CPP (2917, 1999-09-29)
source32\10\AVLT (0, 2006-03-02)
source32\10\BST\MAIN.CPP (3398, 1999-09-29)
source32\10\BST\SNODE.CPP (1747, 1999-09-29)
source32\10\BST\STREE.CPP (1146, 1999-09-29)
source32\10\BST\STREE.H (528, 1999-09-29)
source32\10\BST\TEXTFIX.CPP (1459, 1999-09-29)
source32\10\BST (0, 2006-03-02)
source32\10\BT\MAIN.CPP (3262, 1999-09-29)
source32\10\BT\NODE.CPP (6827, 1999-09-29)
source32\10\BT\NODE.H (421, 1999-09-29)
source32\10\BT\TREE.CPP (3104, 1999-09-29)
source32\10\BT\TREE.H (1471, 1999-09-29)
source32\10\BT (0, 2006-03-02)
source32\10\BUILD\BUILD.CPP (4352, 1999-09-29)
source32\10\BUILD\BUILDTRE.H (408, 1999-09-29)
source32\10\BUILD\MAIN.CPP (3677, 1999-09-29)
source32\10\BUILD\MAIN.EXE (49660, 2000-06-01)
source32\10\BUILD (0, 2006-03-02)
source32\10\SST\MAIN.CPP (2994, 1999-09-29)
source32\10\SST\SPLAYNOD.CPP (5010, 1999-09-29)
source32\10\SST\SPLAYTRE.CPP (370, 1999-09-29)
source32\10\SST\SPLAYTRE.H (475, 1999-09-29)
source32\10\SST (0, 2006-03-02)
source32\10 (0, 2006-03-02)
source32\11\BTREE\BNODE.CPP (15038, 1999-09-29)
source32\11\BTREE\BNODE.H (196, 1999-09-29)
... ...

This directory contains all software implemented for the book: Data Structures and Program Design in C++ by Robert L. Kruse and Alexander J. Ryba The directory is divided up into subdirectories named 1, 2, ... 13, b, c. Each directory contains all software associated with the corresponding chapter or appendix. This software consists of implementations and drivers for programs, functions, and methods in the text, for exercises in the text, and for the programming projects. The solutions to the programming projects are designed to be complete and user friendly programs. For each project a README file describes what component code is included. The drivers for software from the text and exercises are designed merely to test that code is implemented correctly. The solution to a particular project can be located as follows: If the project is numbered X in Section Y of Chapter Z, then its solution is in the directory: Z/YpX Thus for example the solution to Project P1 from Section 2 of Chapter 2 can be found in the directory 2/2p1 (that is the subdirectory 2p1 of the chapter directory 2). In some cases two or more project solutions from a single section are combined into a single solution directory. Thus the directory 6/2p1p2 contains solutions to Projects P1 and P2 from Section 2 of Chapter 6. Also 4/5p1__p5 contains solutions to Projects P1,P2,P3, P4, and P5 from Section 5 of Chapter 4. Any software associated with exercises in the text can be located by the following similar naming scheme: If the exercise is numbered X in Section Y of Chapter Z, then its solution is in the directory: Z/YeX Thus for example the solution to Exercise E2 from Section 5 of Chapter 1 can be found in the directory 1/5e2 (that is the subdirectory 5e2 of the chapter directory 1). In some cases two or more exercise solutions from a single section are combined into a single solution directory. Thus the directory 10/3e2e3e4 contains solutions to Exercises E2, E3 and E4 from Section 3 of Chapter 10. Also 10/1e1__e16 contains solutions to Exercises E1 through E16 of Section 1 of Chapter 10. The software described in the text itself can generally be found in named subdirectories of the corresponding chapter directories. Thus the directory 6/editor contains the software for the editor project of Chapter 6 (Section 4). In many cases, programs reuse and include software developed in other parts of the text. For example, in the Graph implementations of Chapter 12, we use List implementations from Chapter 6 wherever convenient. Our programs simply use a #include directive. Readers of the programs can also follow these directives to piece together the complete set of components in a solution. These programs have been tested under the g++ compiler (version 2.7.2.1) and the Borland compiler (version 5.0). Some older compilers might not recognize the type bool which we have used in many programs. If this causes problems the utility file (of Appendix C) c/utility.h should be replaced by the alternative version c/old_util.h which inlcudes a simple simulation of the type bool. These and other possible modifications to the utility file are discussed in Appendix C. An ANSI-C++ version of the utility file: c/ansiut.h can be used to replace utility.h for ANSI-C++ compilers.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：