Paul,
Regarding 'unpaired left bracket' report, I could imagine that gFortran would report the line of code and also place a '1' under that unpaired left bracket, not that I am familiar with this message in gFortran.
Could it be possible for FTN95 to provide an indicator of the position of the offending line of code and the position of this lonely bracket ? For the case of Dan's 100's of continuation lines, it would also be important to identify the correct line of code. (Often the line number is the start of the continuation, rather than the line in the 100's of lines.)
The other related type of error that I have found confusing is when I omit an END IF or END DO in a multi-level IF or DO coding, the reporting is not always clear. Could the report identify the IF or DO level where the problem was identified or the range of lines associated with this DO or IF structure. (This could be identified by BOTH the line where the IF started and the line where it was identified it was not terminated.) Often, I have coded with my informative (to me) indents, but they are not recognisable to the compiler. It becomes difficult to identify the mistake as the code looks clearly set out! Could the .lis report annotate DO or IF by there start and end levels ?

