Program termination: Difference between revisions

end f</lang>

Memory is automatically managed and reclaimed by AppleScript.

=={{header|ARM Assembly}}==

{{works with|as|Raspberry Pi}}

To end not just the current process, but all processes in the same group, do <lang C>exit_group();</lang>

=={{header|C++}}==

Note that returning a value from main is mostly equivalent to calling <tt>std::exit</tt> with the returned value, except that automatic variables are correctly destructed. If one wants to return from an inner function, while still doing complete cleanup, a solution is to throw an exception caught in main (this will call the destructors of non-main local variables during stack unwinding), and to then return normally from main (which will destruct all automatic objects in main, and then do the cleanup like <tt>std::exit</tt>.

=={{header|Clojure}}==

if problem ->

halt().</lang>

=={{header|Forth}}==

exit code is 1

</pre>

=={{header|Gambas}}==

(and the stack trace follows)

</pre>

=={{header|Groovy}}==

Solution #1:

<lang groovy>if (problem) Runtime.runtime.halt(intExitCode)</lang>

=={{header|Haskell}}==

<lang javascript>if (some_condition)

quit();</lang>

=={{header|jq}}==

The following is functional. Better practice is to instead jump to commands or subs to close known open files, windows etc, avoiding error messages as above.

<lang lb>if 2 =2 then end</lang>

=={{header|Logo}}==

{{works with|UCB Logo}}

An exit without these cleanups can be done with <code>POSIX::_exit()</code> (as noted in <code>perlfunc.pod</code> under the normal <code>exit()</code>). This is the <code>_exit()</code> system call (which the C library generally provides in equivalent form on non-Unix/non-POSIX systems too).

=={{header|Phix}}==

(custodian-shutdown-all (current-custodian)))

</lang>

=={{header|REBOL}}==

}

</lang>

=={{header|Scheme}}==

Sys.exit(code);

}</lang>

=={{header|Simula}}==

<lang Simula>IF terminallyIll THEN terminate_program;</lang>»The procedure "terminate_program" terminates program execution. It&nbsp;closes SYSIN&nbsp;and&nbsp;SYSOUT.

&nbsp;&nbsp;It is implementation-dependent with respect to whether or not other open files are also closed.« [[http://simula67.at.ifi.uio.no/Standard-86/chap_10.htm| Simula Standard 86]]

=={{header|SNOBOL4}}==

-> execution stops and message:

IF (condition==2) ERROR/STOP "condition ",condition, " Execution STOP "</lang>

=={{header|UNIX Shell}}==

fi

exit 0 # Program terminated normally</lang>

=={{header|Ursa}}==

If problem then Application.Quit

'This will stop the application, but will prompt you to save work.</lang>

=={{header|VBScript}}==

next

loop</lang>

=={{header|Visual Basic}}==