Files in this directory:

classes?.ps - PC-Choices class hierarchy chart.
classidx.ps - PC-Choices class index; tells you which file defines a
given class.
classidx.txt - Same as classidx.ps.
fileidx.ps - PC-Choices file index; tells you what classes are defined in
a given file.
fileidx.txt - Same as fileidx.ps.
overview.ps - PC-Choices overview.
pcc.doc - General information on PC-Choices.
pccapp.doc - General information on application compilation environment.
progapp.ps - Primer on programming applications.
progapp.txt - Same as progapp.txt.
struct.ps - Structure of PC-Choices.
virtualpc.ps - VirtualPC framework in PC-Choices for DOS/Choices cooperation.

Files with the .ps suffix are PostScript files; files with the .txt suffix
are ASCII files. The ASCII files look untidy because they were produced
from DVI files. Whenever possible, use the PostScript files.
0. DO NOT USE BITMAPS - I HAVE CHANGED THEM

1. The new libraries have 2 distinct sets of classes. One set
uses virtual functions, which means you have the space
overhead of the vtable pointer per object. This can be
serious where a large collection of those objects is used.

2. In the other set, the individual objects do not have
virtual functions. This includes Links and Lists. In this
case, virtual functions are simulated by passing a pointer
to a function dispatcher, called the FooVirtualiser for a
class Foo. The virtualiser itself has virtual functions,
and the subclasses operate on parameters by proper
typecasting.

2.5 The "NV" classes are doubly linked lists without virtual functions.

The files for these classes are all prepended with "Light".

3. The HashTable subclasses, for both the "Light" and
nonlight classes, illustrate usage of the classes.
MultiHashTables use overloading to give HashTables that can
have multiple types of objects. AssocTables do the same for
pairs where the object is the index. These are
not really designed to be subclassable. If they do not suit
your needs (for special entries etc.), subclass HashTable.

Look up Kernel/ObjectProxyManager.cc for an example.

4. There is a test suite for the libraries. Libraries are
intended to be tested under Unix. If you decide to add
something, create a proper test suite. See the Makefile to
find out how the suite operates.

5. The incoming directory contains sources that were not tested in
this stable, since they are not used. In the next stable, they will be
tested. The incoming/maybe directory contains sources that are semi-written.

WARNING: The files in this directory are not to be compiled with
applications or libraries! includes/system should be used instead.

These files are the original system header files that were used
to produce the stripped header files in includes/system which
define the kernel interface for applications. Protected kernel
components and comments have been stripped from the original files.
The files are provided here so that you may use them as documentation,
but otherwise they serve no purpose in the application development
package.
The files in this directory are kernel interface files used for
compiling applications. These files are stripped versions
of kernel header files. Please refer to includes/system2 for
the original header files, which contain more documentation.
Directories:

app - Application source code, application compilation directory.
bin - PC-Choices kernel, kernel bootstrapper, Chocs (Choices command
shell), Chocs profile.
cbin - Application binaries.
doc - Documentation on application programming.
include - System include files for application compilation.
lib - Application libraries.
src - Source code for loadcoff, the kernel bootstrapper.