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
In my understanding this is more or less a no-operation if the return-if is not top-level in the procedure - lets say inside an if (will continue after the if) or even worse inside a loop (may behave a bit like a continue and jump to the next iteration). In either case the return value is lost.
If I'm correct currently I think that fixing this is not completely trivial since in my opinion in true case this block should leave the procedure without any further execution. When I find the time I will do some investigations in Blockly.Net where there is even one more challenge due to the try/catch/finally block - finallies should be executed in full. Could be a mess...
Addition: as far as I understand the code generation will work as expected since it generates a return statement!
The text was updated successfully, but these errors were encountered:
https://github.com/richorama/IronBlock/blob/master/IronBlock/Blocks/Procedures/ProceduresIfReturn.cs checks the condition and either returns the indicated value or continues execution.
In my understanding this is more or less a no-operation if the return-if is not top-level in the procedure - lets say inside an if (will continue after the if) or even worse inside a loop (may behave a bit like a continue and jump to the next iteration). In either case the return value is lost.
If I'm correct currently I think that fixing this is not completely trivial since in my opinion in true case this block should leave the procedure without any further execution. When I find the time I will do some investigations in Blockly.Net where there is even one more challenge due to the try/catch/finally block - finallies should be executed in full. Could be a mess...
Addition: as far as I understand the code generation will work as expected since it generates a return statement!
The text was updated successfully, but these errors were encountered: