special hair in the compiler for unbalanced parentheses

[MOON at SCRC-TENEX]

It seems to me that the Find Unbalanced Parentheses command in the editor
is in a much better position to tell you where the unbalanced parentheses
are than the compiler, and the job should be left to it.

If it takes any significant amount of hair to make the compiler recover\n from missing close parenthesis errors, I can't see that it is worth it.
I don't think it saves the user much time to try to compile the rest of the
file, since it doesn't take nearly as long to read through the file and
not compile it (as it does now) as to compile it.