`J.T. Conklin' changed the state to `analyzed'.


State-Changed-From-To: open-analyzed
State-Changed-By: jtc
State-Changed-When: Mon Jul 25 10:30:33 1994
State-Changed-Why:
My vote is for replacing true and false with shell scripts.  

Now that the shell has a true and false builtin (as required by
POSIX.2), we could implement the scripts as follows:

	#!/bin/sh
	true

and
	#!/bin/sh
	false

But if a user replaced /bin/sh with something without the builtins, it
would go into an infinate loop.  I think this is a quality of
implementation issue that we'd rather avoid.

If I remember correctly, the AT&T "true" was just a big copyright
notice, and "false" was a big copyright notice followed by "exit 255".
So, there should be no problem wrt. copyright infringment if our true
implementation was "exit 0" and our false implementation was "exit 1".

The minimum shared executable size is a separate issue and should be
submitted as a separate PR.


------------------------------------------------------------------------------