🚀 go-pugleaf

Because I installed C++ under LOCUS, a distributed UNIX supporting both the
SysV and bsd environments, I've had installation experiences with both.  Some
notes:

Both environments:

    Compiling lib/stream/out.c provokes a warning.  To eliminate it, add this
    declaration:     void exit(int);

BSD environment:

    test(1)'s argument parsing has a bug, so in the CC script, change
	if test "$R" -a ! "$PLUSI"
    to
	if test -n "$R" -a ! "$PLUSI"

    Many BSD installations have modified sh(1) so that if a script starts with
    "#", the C shell is invoked to process it.  For those sites, insert
	#!/bin/sh	to be the first line of scratch/bsd.sed, and swap
    the lines   #!/bin/sh   and   #ident ...   in the CC script.

Suggestions for Release 1.1:

    Include a machine-readable man page for CC.
    Have the CC man page document all the CC flags (e.g. +i).
    If CC remains a shell script,
       Change __err, __cdtd.c, __cdtd.o to __err$$, __cdtd$$.c, __cdtd$$.o;
	   this allows concurrent compilations, a nice benefit of a distributed
	   system.
       Change   munch   to   $munchC  , and define the variable a` la cfrontC.

-- David Smallberg, das@locus.ucla.edu, {ihnp4,ucbvax}!ucla-cs!das