The basic idea: Read in a text file, and use indentation cues to know when
to insert open/close braces.  The intention is to let you write C-like
source code in a more readable, less error-prone fashion (no braces to
distract/balance).

The output is kept reasonably readable, with optional #line directives to
get compiler-warnings/errors to correspond correctly.  (Have the #line
directives generated if you are using auto-braces as a transparent step
during compilation; have the #line directives disabled if you plan to
_read_ the output of auto-braces.)

It is, more or less, a HACK.  That is, it does not really grok C syntax,
and could behave more intelligently than it does, in several ways.  To its
credit, though, it does recognize existing braces already in the file.

(Note: "Aminet.Uploader@olib.org" is in one sense exactly the same as
 "rkr@olib.org", but the Aminet.Uploader "user" mailbox exists so that I
 can have my mail automatically seperated somewhat as it arrives.  olib.org
 is my Amiga, running AmiTCP/IP.)

 PERMSSN    UID  GID    PACKED    SIZE  RATIO METHOD CRC     STAMP          NAME
---------- ----------- ------- ------- ------ ---------- ------------ -------------
[generic]                 6767   20717  32.7% -lh1- 02d8 May  6  1994 auto-braces/ab.c
[generic]                 7484   11516  65.0% -lh1- dd2d Apr 29  1995 auto-braces/auto-braces
[generic]                 6163   17202  35.8% -lh1- 6dd2 May  6  1994 auto-braces/auto-braces.c
[generic]                 4586   10805  42.4% -lh1- fe0c May  6  1994 auto-braces/auto-braces.doc
[generic]                  175     265  66.0% -lh1- b280 Oct 25  1993 auto-braces/auto-braces.test
[generic]                  619     981  63.1% -lh1- b928 Apr 29  1995 auto-braces/copyright
[generic]                  674    1146  58.8% -lh1- e27d Apr 30  1995 auto-braces.readme
---------- ----------- ------- ------- ------ ---------- ------------ -------------
 Total         7 files   26468   62632  42.3%            May  2  1995