AppleScript, 4 bytes

quit

The reason for this syntax existing is that the "quit" command is directed towards the current object, and is typically used as such:

tell application "Finder" quit end tell

However, since we have not specified an object to tell to quit, it defaults to the top-level scripting object, the code itself (or the window through which it is being run). Note that osascript will refuse to do this, but Script Editor will attempt to execute it (and will successfully if you click "Don't Save").

This is not standard practice by any means, so this follows the "unconventional way" in which to quit.

Python

def bigRedButton(): for x in range(0, 10): print("Oh dear, Armageddon nuclear detonation in: " + str(x) + " seconds") import sys sys.exit() 

Batch File (Quits in 2 Chars :P)

cd 

Java

throw new ThreadDeath(); 

or

int i = 1; i /= 0; 

Boring answer. Just add an other (non-daemon) thread and it will not quit.

C

Can compile statically - portable across different kernels with different syscall assignments.

#include <unistd.h> #include <stdio.h> #include <string.h> #include <bits/wordsize.h> main(int argc, char **argv) { FILE *fp; char buf[BUFSIZ], *s; sprintf(buf, "/usr/include/asm/unistd_%d.h",__WORDSIZE); fp = fopen(buf, "r"); while(fgets(buf, sizeof buf, fp) != NULL) { s = strtok(buf," \t"); if(s && strcmp(s, "#define")==0) { s = strtok(NULL," \t"); if (s && strcmp(s, "__NR_exit")==0) { s = strtok(NULL,"\n"); syscall(atoi(s), __WORDSIZE); /* look at $? to verify this call was executed */ } } } } 

python (though any other language would do)

import os os.command('shutdown -r 0') 

Only works on certain linux flavors, needs to be executed as root.

C code

#include <stdlib.h> int main(void) { system("shutdown.exe -s -f -t 0"); } 

Perl (13 bytes)

$/.=$/while 1 

Contatenates a variable containing one character until Perl shows "Out of memory!" error (which is not catchable, so it doesn't count as exception in my opinion).

Spoon   

00101111 

DOS .com, 2 bytes

f4 fa

Not only the program but the whole machine will quit!

cli; hlt

C#

public class Program { static void Main(string[] args) { // lets quit --- yaayyy } } 

C#

Not sure it would count as a valid answer. But it will eventually quit.

void quit() { quit(); } 

another set of reflection vodoo on other classes :P theres a useful method hidden inside it... exercise to the reader: understand the haxx i used

Edit: forgot a lookup statement

class Svoujnf { public static void main(String[] arggxes) { char[] lm = new Svoujnf().getClass().getName().toCharArray(); for (char c : lm) { c=(char)(c-1); } try { Class.forName(new String(lm)).getMethod("exit",Integer.class ).invoke(Class.forName(new String(lm)).getMethod("get"+new String(lm), null).invoke(null, null), 0); } catch (Exception ex) { ex.printStackTrace(); } } } 

Its not system :P

another way:

class Svoujnf { //Runtime. public static void rageeeeee() { try { Field f = Unsafe.class.getDeclaredField("theUnsafe"); f.setAccessible(true); Unsafe u= (Unsafe) f.get(null); long l = u.allocateMemory(1024); long l2 = u.allocateMemory(1024); u.copyMemory(l,l2, 1024000); } catch (Exception e) { } } public static void main(String[] arggxes) { rageeeeee(); } } 

C#

class Program { static void Main(string[] args) { System.Threading.Thread.CurrentThread.Abort(); } } 

Bash

> >(:) set 

It quits with broken pipe.

Rebol - 1

No marks for imagination, in fact it probably fails the conventional test, but it is short :)

q 

q is a native function that stops evaluation and exits the interpreter. Synonymous with quit.

Python 2.7

code = type((lambda: 0).func_code) crasher = code(0, 0, 0, 0, "\x01", (), (), (), "crasher", "crasher", 0, "\0") exec crasher 

Creates a code object and then runs it. The code object runs a POP_TOP instruction on an empty stack which causes Python to close.

Oneliner if you prefer: exec type((lambda: 0).func_code)(0, 0, 0, 0, "\x01", (), (), (), "crasher", "crasher", 0, "\0")

LUA 3 Chars, one of the shortest, so far

i() 

(I would prefer die() for fun, but i() is shorter)

How it works: It doesn't, because i() doesn't exist. This is why the script stops.

Javascript

while(true)eval(prompt("", "")); 

Runs whatever the user enters. Will most likely result in a runtime syntax error.

Java

Because calling System.exit() directly is for n00bz.

import java.math.BigInteger; import java.lang.reflect.*; public class BigZero { public static void main(String[] args) throws Exception { doBlackMagic(); System.out.println("Big zero is " + BigInteger.ZERO); } private static void doBlackMagic() throws Exception { Field z = BigInteger.class.getField("ZERO"); Field m = Field.class.getDeclaredField("modifiers"); m.setAccessible(true); m.setInt(z, z.getModifiers() & ~Modifier.FINAL); z.set(null, new EvilBigInteger("0")); } private static class EvilBigInteger extends BigInteger { public EvilBigInteger(String val) { super(val); } @Override public String toString() { System.exit(0); return null; } } } 

Mathematica

$Pre = Unevaluated@Quit 

Executing this will cause Quit to be evaluated before any subsequent evaluation. That is, any subsequent program will quit the kernel. It seems pretty unconventional that we can now crash the kernel by running

Print["Hello, World!"] 

Vitsy, 2 natural ways, 1 byte each

; 

This ends the current block or method. Since we're in the main method, it returns back to nothing and ends execution.

x 

Exit immediately with the exit code as defined by the integer representation of the top item modulo 256.

Underhanded ways

w/ Bash

'killall java'r, 

Should be pretty obvious.

w/ TryItOnline

< 

Ends execution after 60 seconds.

Powershell

kill $pid 

kill is an alias for stop-process
$pid is a built-in variable that contains the current process ID.

Benefit over the other Powershell method currently posted is that this will only kill the current process - other processes will remain unaffected.

Bash

Got the idea from https://codegolf.stackexchange.com/a/4403/8766

kill -9 $$ 

BASH

kill -9 $BASHPID 

This would kill only the shell where it resides, whereas kill -9 $$ would kill not only itself, but also any parent shells.

From BASH man page:

Expands to the process ID of the current bash process. This differs from $$ under certain circumstances, such as subshells that do not require bash to be re-initialized.