reading close

[LEBRUN at PARC-MAXC]

It would be nice to get better error recovery, but having it depend on
character coulmns too heavily is, well, Fortranoid.  It's OK for the
editor to use such cues as an efficiency hack (I guess) but the compiler
ought to be able to work with any format, no matter how ugly.

I think the idea of using something like #@ as READ "synchronization
marks" is a fine idea, but I dislike having "white space" mean anything
very special.

Certainly any (untrapped) error ought to be reported and not inhibited
by text formatting style?

One possibility would be for various pieces of compiler state be
reported on reading a CLOSE, for example: whether inside a string, sexpr
or whatever, and perhaps nesting level and the position of the start of
the current top-level or other "unfinished" form.

-------