Project

General

Profile

Support #1603

Unhelpful behaviour in "compatibility mode": double error mesg

Added by John Abbott almost 3 years ago. Updated about 1 month ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Parser/Interpreter
Target version:
CoCoA-5.4.2
Start date:
12 Jul 2021
Due date:
% Done:

0%

Estimated time:
Spent time:
0.10 h

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 about 1 month 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?)

Also available in: Atom PDF