|
Post by tsh73 on Mar 17, 2024 16:27:26 GMT -5
Windows 32 bit I worked with really long (1000+) lines program in foreign BASIC (QB64) (this one qb64.com/samples/torus-demo/ ) Obviously there are things that is "wrong" from LB' point of view.
Expected behavior: LB should stop at error line, and highlight it. And it better be FIRST error.
That happens in LB5 353: status line says "Syntax error in line 13:$NoPrefix'" but editor is scrolled full way to bottom (1000+ lines!) and part of the code from error down to last line is selected.
(Just for a record, LB4.51 just errors
No offending line is mentioned /selected Log file mentions
It surely looks wrong for LB
Sub CountTiles (T1 As Integer, T2 As Integer) Static but 1) I have to look at Log file for it. It is not for mere humans so it has no line number as well, had to search 2) it is at line 263 - surely not first error? )
|
|
|
Post by Marco Kurvers on Mar 21, 2024 9:35:59 GMT -5
The different with QB is that you cannot use parentheses in a SUB and in a FUNCTION. You cannot use a STATIC. Static subs or not, LB uses only the command SUB or FUNCTION.
If you will try to find where an error is, use breakpoints. If the error comes earlier than the breakpoint, you know that the error is not after the breakpoint. Comes the breakpoint earlier, you can remove the breakpoint and place a new breakpoint, for example, 20 lines further and debug the program again, etc.
|
|
|
Post by tsh73 on Mar 21, 2024 11:16:08 GMT -5
|
|