Page 1 of 1

Compiler Error Check order

Posted: Sun Feb 19, 2017 12:48 pm
by Num3
It's me again xD

I think unclosed keywords should have precedence to invalid placement rules, take this example.
You will never be able to stop the bad IF, if it is somewhere else far away on the code.

Code: Select all

If test

;
; Gazilion lines of code
;

  
  Procedure upsss() ; Error checking at first procedure inside the IF keyword
  EndProcedure
  

Re: Compiler Error Check order

Posted: Mon Feb 20, 2017 7:07 am
by Fred
Not a bug, the error is properly reported :).

Re: Compiler Error Check order

Posted: Tue Feb 21, 2017 6:05 pm
by Num3
Yes, the error is correct.
My argument is that the unclosed IF should be reported first, because it has precedence.
:ugeek:

Re: Compiler Error Check order

Posted: Wed Feb 22, 2017 8:00 am
by Fred
The compiler stops at the first encounter error. It doesn't even know you didn't closed the If, as it didn't go further.