Bug 77067

Under certain circumstances, 'set -e' causes /bin/sh to exit when it should
not. From the manpage:

     -e errexit
             Exit immediately if any untested command fails in non-interactive
             mode.  The exit status of a command is considered to be explic-
             itly tested if the command is used to control an if, elif, while,
             or until; or if the command is the left hand operand of an `&&''
             or `||'' operator.

However, there are circumstances where even when a command status is
explicitly tested the script still terminates. I can replicate this using a
function call.

How-To-Repeat: 
This script demonstrates the problem:

------------------------------------------------------------
#!/bin/sh

set -e

foo ( ) {
  if test "x$1" != "xyes"; then
    return 1
  fi
  echo "OK!"   # this line causes the problem!
}

if foo yes; then echo "yes"; fi
if foo no; then echo "no"; fi
echo "Completed!"
------------------------------------------------------------

It fails to complete. However, if you remove the 'echo "OK!"' line it *does*
complete. (This line can be anything - for example, replacing it with
"return 0" also causes the problem).

The script runs correctly under 'bash', so I don't think my understanding of
-e semantics is broken.