# Exception handling syntax

Exception handling syntax is the set of keywords and/or structures provided by a computer programming language to allow exception handling, which separates the handling of errors that arise during a program's operation from its ordinary processes. Syntax for exception handling varies between programming languages, partly to cover semantic differences but largely to fit into each language's overall syntactic structure. Some languages do not call the relevant concept "exception handling"; others may not have direct facilities for it, but can still provide means to implement it.
Most commonly, error handling uses a try...[catch...][finally...] block, and errors are created via a throw statement, but there is significant variation in naming and syntax.

## Catalogue of exception handling syntaxes
### Assembly language

Most assembly languages will have a macro instruction or an interrupt address available for the particular system to intercept events such as illegal op codes, program check, data errors, overflow, divide by zero, and other such. IBM and Univac mainframes had the STXIT macro. Digital Equipment Corporation RT11 systems had trap vectors for program errors, i/o interrupts, and such. DOS has certain interrupt addresses. Microsoft Windows has specific module calls to trap program errors.

### Bash

One can set a trap for multiple errors, responding to any signal with syntax like:
    trap 'echo Error at line ${LINENO}' ERR

### BASIC

An On Error goto/gosub structure is used in BASIC and is quite different from modern exception handling; in BASIC there is only one global handler whereas in modern exception handling, exception handlers are stacked.

### C

C does not provide direct support to exception handling: it is the programmer's responsibility to prevent errors in the first place and test return values from the functions.
In any case, a possible way to implement exception handling in standard C is to use setjmp/longjmp functions:

#### Microsoft-specific

Two types exist:
* Structured Exception Handling (SEH)
* Vectored Exception Handling (VEH, introduced in Windows XP)
Example of SEH in C programming language:

### C#

A try block must have at least one catch or finally clause and at most one finally clause.

### C++

In C++, a resource acquisition is initialization technique can be used to clean up resources in exceptional situations. C++ intentionally does not support finally. The outer braces for the method are optional.

### ColdFusion Markup Language (CFML)
#### Script syntax

Adobe ColdFusion documentation

#### Tag syntax

Adobe ColdFusion documentation

#### Railo-Lucee specific syntax

Added to the standard syntax above, CFML dialects of Railo and Lucee allow a retry statement.
This statement returns processing to the start of the prior try block.
CFScript example:
Tag-syntax example:

### D

In D, a finally clause or the resource acquisition is initialization technique can be used to clean up resources in exceptional situations.

### Erlang
### F#

In addition to the OCaml-based try...with, F# also has the separate try...finally construct, which has the same behavior as a try block with a finally clause in other .NET languages.
For comparison, this is a translation of the C# sample above.
For comparison, this is translation of the OCaml sample below.

### Haskell

Haskell does not have special syntax for exceptions. Instead, a try/catch/finally/etc. interface is provided by functions.
prints
in analogy with this C++
Another example is
In purely functional code, if only one error condition exists, the Maybe type may be sufficient, and is an instance of Haskell's Monad class by default. More complex error propagation can be achieved using the Error or ErrorT monads, for which similar functionality (using `catch`) is supported.

### Java

A try block must have at least one catch or finally clause and at most one finally clause.
If multiple resources are acquired, the correct way to deal with them is with nested try blocks. For this reason and others, try-with-resources was added to the language to almost entirely replace finally clauses. Resources acquired in a parentheses after the try keyword will be cleaned up automatically. Classes used in these statements must implement an interface called AutoCloseable.

### JavaScript

The design of JavaScript makes loud/hard errors very uncommon. Soft/quiet errors are much more prevalent. Hard errors propagate to the nearest try statement, which must be followed by either a single catch clause, a single finally clause, or both.
If there is no try statement at all, then the webpage does not crash. Rather, an error is logged to the console and the stack is cleared. However, JavaScript has the interesting quirk of asynchronous externally-invoked entry points. Whereas, in most other languages, there is always some part of the code running at all times, JavaScript does not have to run linearly from start to end. For example, event listeners, Promises, and timers can be invoked by the browser at a later point in time and run in an isolated but shared context with the rest of the code. Observe how the code below will throw a new error every 4 seconds for an indefinite period of time or until the browser/tab/computer is closed.
Another interesting quirk is polymorphism: JavaScript can throw primitive values as errors.
Note that the catch clause is a catch-all, which catches every type of error. There is no syntaxical ability to assign different handlers to different error types aside from experimental and presently removed Gecko extensions from many years ago. Instead, one can either propagate the error by using a throw statement inside the catch statement, or use multiple conditional cases. Let us compare an example in Java and its rough equivalents in JavaScript.
Another aspect of exceptions are promises, which handle the exception asynchronously. Handling the exception asynchronously has the benefit that errors inside the error handler do not propagate further outwards.
Also observe how event handlers can tie into promises as well.
Lastly, note that, as JavaScript uses mark-and-sweep garbage-collection, there is never any memory leakage from throw statements because the browser automatically cleans dead objects—even with circular references.

### Lua

Lua uses the pcall and xpcall functions, with xpcall taking a function to act as a catch block.

#### Anonymous function
### Next Generation Shell
#### Ignoring exceptions - "tor" operator

"tor" is try-or operator. In case of any exception when evaluating the argument on the left, evaluates to the argument on the right.

#### "block" - facility to use exceptions to return a value
### Perl 5

The Perl mechanism for exception handling uses die to throw an exception when wrapped inside an eval { ... }; block. After the eval, the special variable $@ contains the value passed from die.
Perl 5.005 added the ability to throw objects as well as strings. This allows better introspection and handling of types of exceptions.
The __DIE__ pseudo-signal can be trapped to handle calls to die. This is not suitable for exception handling since it is global. However it can be used to convert string-based exceptions from third-party packages into objects.
The forms shown above can sometimes fail if the global variable $@ is changed between when the exception is thrown and when it is checked in the if ($@) statement. This can happen in multi-threaded environments, or even in single-threaded environments when other code (typically called in the destruction of some object) resets the global variable before the checking code. The following example shows a way to avoid this problem (see or ; cf. ). But at the cost of not being able to use return values:
Several modules in the Comprehensive Perl Archive Network (CPAN) expand on the basic mechanism:
* Error provides a set of exception classes and allows use of the try/throw/catch/finally syntax.
* TryCatch, Try::Tiny and Nice::Try all allow the use of try/catch/finally syntax instead of boilerplate to handle exceptions correctly.
* Exception::Class is a base class and class-maker for derived exception classes. It provides a full structured stack trace in $@->trace and $@->trace->as_string.
* Fatal overloads previously defined functions that return true/false e.g., open, close, read, write, etc. This allows built-in functions and others to be used as if they threw exceptions.

### PowerBuilder

Exception handling is available in PowerBuilder versions 8.0 and above.

### S-Lang

New exceptions may be created using the new_exception function, e.g.,
will create an exception called MyIOError as a subclass of IOError. Exceptions may be generated using the throw statement, which can throw arbitrary S-Lang objects.

### Smalltalk

The general mechanism is provided by the message on:do:. Exceptions are just normal objects that subclass Error, you throw one by creating an instance and sending it a #signal message, e.g., MyException new signal. The handling mechanism (#on:do:) is again just a normal message implemented by BlockClosure. The thrown exception is passed as a parameter to the handling block closure, and can be queried, as well as potentially sending #resume to it, to allow execution flow to continue.

### Swift

Exception handling is supported since Swift 2.

### Tcl

Since Tcl 8.6, there is also a try command:

### Visual Basic 6

Exception handling syntax is very similar to Basic. Error handling is local on each procedure.
Example of specific (non official) implementation of exception handling, which uses object of class "Try".

#### Visual Basic .NET

A Try block must have at least one clause Catch or Finally clause and at most one Finally clause.