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 debugging, when the debugger enters the FOR, it should go back to the for line as it has an assignation and then go to the inside block, in this case, it will always mark the print(i) but not the assignation.
Also, after finishing the for, for some reason it enter the else of the IF above. Which is more important bug.
Here is the code:
`x = 1;
x++;
if (x < 10) {
for (i = 1; i < 10; i++) {
print(i);
}
} else {
print("hola2");
}_`
The text was updated successfully, but these errors were encountered:
Hola, yes, you are absolutely right, will be fixing this.
The first one was actually a known (not-implemented) feature but the second one is a bug indeed (was not discovered since shown only when debugging step by step, somehow not when running all code at once).
Thanks,
Vassili
Hello, I think I found a new error while debugging, in fact there are 2 errors:
https://gyazo.com/1aa6094c8b440dd08b449c3bfde36755
Check this video,
When debugging, when the debugger enters the FOR, it should go back to the for line as it has an assignation and then go to the inside block, in this case, it will always mark the print(i) but not the assignation.
Also, after finishing the for, for some reason it enter the else of the IF above. Which is more important bug.
Here is the code:
`x = 1;
x++;
if (x < 10) {
for (i = 1; i < 10; i++) {
print(i);
}
} else {
print("hola2");
}_`
The text was updated successfully, but these errors were encountered: