Support #1603
Unhelpful behaviour in "compatibility mode": double error mesg
Description
Syntactic errors inside compatibility mode can be unhelpful:
/**/ f := ***2x;*** g:=3; // semicolon should be outside compat-mode --> ERROR: Semicolons are not allowed inside backward-compatibility markers (exiting backward-compatibility mode) --> f := ***2x;*** g:=3; // semicolon shoul ... --> ^ --> ERROR: I was expecting a compatibility marker but I've found the operator/symbol ":=" --> f := ***2x;*** g:=3; // semicolon should be out ... --> ^^ /**/
Not sure what to do here.
Just leave it like this?
History
#1
Updated by John Abbott 4 months ago
I'm very tempted to mark this one won't fix.
It would likely be a lot of work modifying the parser/interpreter, and without any assurance that we'd find a better solution.
I suspect not many people use the "backward compatibility mode" anyway...
Reject? (or do we have a won't fix conclusion option?)
#2
Updated by John Abbott about 2 months ago
I'm still with won't fix because we have far more important things to do with our time.
Reject?
#3
Updated by Anna Maria Bigatti about 2 months ago
- Status changed from New to Rejected
- % Done changed from 0 to 100
John Abbott wrote:
I'm still with won't fix because we have far more important things to do with our time.
Reject?
I agree. It is a rare problem and not worth the effort.