file: readme.uts  date: 9/10/83   author: David H. Wolen

This disk contains the source for the UTOOLS -- a set of utility programs
I recently submitted to the foglib.  See the appropriate foglib disks for
user oriented documentation.  The programs are written in C, using
version 1.46 of the BDS compiler.  The following notes about bringing
up the UTOOLS on your own are disorganized and probably
incomplete -- that should be fair warning.  Also, note that you'll need
some files from the BDS C distribution package to complete this package.
I'm not including them because I'm not sure if the source for them is
public domain.

1.   I've enabled alloc and free by making the appropriate change to bdscio.h
     and recompiling the indicated libraries.  See the instructions in
     bdscio.h.  Alloc and free are only (I think) used by the tail tool.
     The other tools that  do storage allocation don't need to free it so
     they use sbrk instead (reducing memory requirements and the size of
     the .com file).

2.   I've enabled console buffering by making the appropriate change to dio.h.
     See the instructions in dio.h.
3.   Just about all the UTOOLS use something from mylib3.c.  I've made it
     my deff3.crl.  There are probably some routines on mylib3.c that 
     aren't used by the UTOOLS.
     Note -- there's a bug in 1.46 that prevents deff3.crl
     from being picked up automatically if you compile with source on b
     and b as the logged drive.

4.   Before my upgrade to double density, I kept dio.h and dio.crl on the
     same drive as the source.  With double density, I keep everything
     but the source on A and compile with A as the logged drive.  Some
     of the "linkage" comments in the source code reflect the first method, 
     while others reflect the second -- you've been warned.  Also, you
     may have to change the drive designation in the #include lines to
     correspond to your compile procedure.

5.   The utdir tool needs wildexp.c which comes with the BDS C distribution
     package.

6.   spltscan.c contains a set of character handling functions.  Only
     two of them (I think) are used by a UTOOL (vsplit).  Documentation for
     these functions is on spltscan.doc.  Forgive the few gotos -- this 
     was some of the first C code I wrote.

7.   There are two tools here that I didn't include in the set of .com files
     I submitted to foglib -- lline and makdoc.

8.   I haven't experimented with the compiler options to optimize space or 
     time.  That might be a useful thing for someone to try.

That's all that I can think of that you need to know.  Please forgive any
omissions.
