useless error "end brace required" in comments

../dasm/bin/dasm ./chess.asm -l./chess.lst -f3 -s./chess.sym -o./chess.bin || (echo "mycommand failed $?"; exit 1)
end brace required
end brace required

OK, in which one of my 30+ files are those errors occurring?!!
In fact I'm pretty sure they are because I have pseudocode in commented out code (#if 0), which bugs the hell out of me, because I don't believe the parser should be doing anything but looking for ENDIF (and possiblly nested IF but I'm still out to lunch on that one).

Anyway, there we go - somewhere in "do not assemble this" pseudo-code I obviously have a start brace (a "{" presumably) and there's no matching close one.

PITA to find, and also a PITA having the parser parse it in the first place.

So, I'd like

a) Have the filename and line of the start brace reported, so it's easy to locate
b) provide a way to specify "non-parsed" blocks of text (for example, for comments)

Reproduce the reported dasm command with the chess.asm inputs and trace how the parser handles the unmatched brace inside #if 0 or commented code. Done should include the filename and line for the opening brace and a supported way to mark text as non-parsed, with nested conditional behavior clarified.