Jump to content

Exit 1 reserved


Exit 1 reserved  

13 members have voted

  1. 1. Should a standardized exit code be advised/promoted ?

    • YES: It makes sense to uphold basic meaningful Exit codes
    • NO: An exit error is an exit error. Stop this nonsense !


Recommended Posts

I was looking at an example and it would Exit 1 on error.
So what's wrong with that. Well, we can get an error from different aspects of the script, been the stub errored, or the wrapper errored, or finally, the script.
What I propose is to start script errors on 3 onwards. Been 1 the error of AutoIt3, 2 of the wrapper, and finally the script.

If you agree vote for me: "argumentum 2021" :D

Really, if the concept is sound then say it and if not ... well, say it too  :gathering:

PS: this is in regard to Exit codes of a script and not that of Return in a Function.

Edited by argumentum
clarification

Follow the link to my code contribution ( and other things too ).
FAQ - Please Read Before Posting.
autoit_scripter_blue_userbar.png

Link to comment
Share on other sites

I agree with you, the commonly used exit codes should not be used by the interpreter itself when the script is executing. I'd propose something like reserving a range of exit codes after a large value like 1024...

I will have to think about this too when I finally get around to working on executing code in ECI ;)

EasyCodeIt - A cross-platform AutoIt implementation - Fund the development! (GitHub will double your donations for a limited time)

DcodingTheWeb Forum - Follow for updates and Join for discussion

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...