-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NEW FEATURE: Considerations in returns #159
Comments
They only exist as keywords |
About function commands: |
what if I want to return zero from the cleo function? in opcode form:
how do I write it using just |
oops sorry, I didn't notice that error, I corrected. Yes and thank |
how would I write |
This very risky. The distinction between gosub's and CLEO's return should be obvious. Worst debugging sessions I had was caused by muscle memory and using return instead of cleo_return. Scripts crashes without obvious reason. |
That's the idea. Just like |
Hm, ok. Will it work with functions having multiple exit points? |
|
if you do a code pre-processing, i.e. a text scanner, which identifies the matches and replaces them with the necessary text, there should be no problems with anything. in fact @x87, can't you include in SannyBuilder, a tool to create these auto-replaceable texts? This is something extremely easy to do in JavaScript, with a |
Already done. |
I don't know how to explain this without making it seem redundant...
Syntax
return [value]
Examples
Never use OP
0AA7
or0AA8
, so you are probably typing something nonsensical.The text was updated successfully, but these errors were encountered: