| Search |
|---|
| ID | Rating | Category | Description | Screenshot | Date |
|---|---|---|---|---|---|
| 5178 | 😠 | Suggestion | Add a `return` instruction for behavior The first time around, figuring out what happens when a program runs out of instruction is very confusing, particularly the part where a script implicitly starts over, running forever. After finally having figuring out what exit, break and call do, I'm left with the following problem: I want to write program useable both as subroutines and as standalone program, if anything to debug subroutine unitarily. These behavior are meant to run one time at once. As such, asstandalone program, they would need a final exit statements. But exit statement interrupt the whole behavior, the top level behavior so to speak, so are unsuitable for subroutine. A simple fix would be to make top level behavior implicitly stop rather than restart when running out of instructions, letting the users explicitly wiring their loop if they want the restarting behavior. But I assume there are good design reasons as to why top level behavior implicitly restart, so an other solution would be a return statement, which yields control back to calling context (and terminates if in the top level behavior). | 2025-03-29 00:02:00 |
| ID | Reply | Author | Date |
|---|