In this wiki, we use pseudocode greatly simplify the handlers in order to emphasise some of the more important aspects visually.
We allow missing out of whole sections using "..." and rewriting lines to make them shorter so that they fit into the limited width allowed by wiki. Sometimes this leads to a rewriting of the original handler.
# In computer science
In computer science, __pseudocode__ is a plain language description of the steps in an algorithm or another system.
Pseudocode often uses structural conventions of a normal programming language, but is intended for human reading rather than machine reading - wikipedia 
It typically omits details that are essential for machine understanding of the algorithm, such as variable declarations and language-specific code. The programming language is augmented cognitioned with natural language description details, where convenient, or with compact mathematical notation.
The purpose of using pseudocode is that it is easier for people to understand than conventional programming language code, and that it is an efficient and environment-independent description of the key principles of an algorithm. It is commonly used in textbooks and scientific publications to document algorithms and in planning of software and other algorithms.
No broad standard for pseudocode Syntax (programming languages) exists, as a program in pseudocode is not an executable program, however certain limited standards exist (such as for academic assessment). Pseudocode resembles Skeleton (computer programming), which can be compiled without errors.
Flowcharts, DRAKON and Unified Modeling Language (UML) charts can be thought of as a graphical alternative to pseudocode, but need more space on paper. Languages such as HAGGIS bridge the gap between pseudocode and code written in programming languages.
# Sections
# See also