You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a PL1/PL2 compilation error occurs, a line number is displayed. However, the lines of code are not numbered (furthermore, the line number in the error may change if the compilation is repeated).
"break;" doesn't work for procedures and functions. Error:
Encountered an unknown assembly instruction:
Instruction: BREAK
P.S. I didn't find the functionality of "exit;" function.
Assembler (PL0) commands are not permitted in PL1 and PL2. For example, I would like to use the "HALT" command (because break; didn't worked out, see 2.)
When a program is stopped by HALT, error, or a collision, the number of steps executed is not displayed. It would be nice to see it to assess a performance of an algorithm.
The text was updated successfully, but these errors were encountered:
Thanks for all of these, they are now on the roadmap. We need to
have line numbers in the web UI. Unfortunately, this is JavaScript hacking
make sure than break and continue outside a loop context are invalid. This is a semantic error we need to carefully put in the grammar as a break, for example, in a function should not break. Hacky solution: if BREAK or CONTINUE are remaining in assembly, they were not inside a loop
I think they are
should be easy
this is again javascript hacking, we will do it for the next version
When a PL1/PL2 compilation error occurs, a line number is displayed. However, the lines of code are not numbered (furthermore, the line number in the error may change if the compilation is repeated).
"break;" doesn't work for procedures and functions. Error:
Encountered an unknown assembly instruction:
Instruction: BREAK
P.S. I didn't find the functionality of "exit;" function.
Assembler (PL0) commands are not permitted in PL1 and PL2. For example, I would like to use the "HALT" command (because break; didn't worked out, see 2.)
When a program is stopped by HALT, error, or a collision, the number of steps executed is not displayed. It would be nice to see it to assess a performance of an algorithm.
The text was updated successfully, but these errors were encountered: