The backslash (\) is a typographical mark (glyph) used chiefly in computing. It was first introduced to computers in 1960 by Bob Bemer. Sometimes called a reverse solidus or a slosh, it is the mirror image of the common slash.
Other common terms for the character include hack, escape (from C/UNIX), reverse slash, backslant, and backwhack. Also, it is sometimes referred as bash, reverse slant, reversed virgule, or backslat.
Bob Bemer introduced the \ character into ASCII, on September 18, 1961, as the result of character frequency studies. In particular the \ was introduced so that the ALGOL boolean operators ∧ (AND) and ∨ (OR) could be composed in ASCII as "/\" and "\/" respectively. Both these operators were included in early versions of the C programming language supplied with Unix V6 , Unix V7 and more currently BSD 2.11.
In many programming languages such as C and Perl and in Unix scripting languages, the backslash is used to indicate that the character following it should be treated specially. It is sometimes referred to as a knock-down or escape character. In various regular expression languages it acts as a switch, changing literal characters into metacharacters and vice versa. The backslash is used similarly in the TeX typesetting system and in RTF files to begin markup tags. In Haskell, the backslash is used both to introduce special characters and to introduce lambda functions (since it is a reasonable approximation in ASCII of the Greek letter lambda, λ).
In the context of line-oriented text, especially source code for some programming languages, it is often used at the end of a line to indicate that the trailing newline character should be ignored, so that the following line is treated as if it were part of the current line. In this context it may be called a "continuation". The GNU make manual says, "We split each long line into two lines using backslash-newline; this is like using one long line, but is easier to read."
The Windows API can accept either the backslash or slash to separate directory and file components of a path, but the Microsoft convention is to use a backslash, and APIs that return paths put backslash in. MS-DOS 2.0 copied the hierarchical file system from Unix and thus used the forward slash, but (possibly on the insistence of IBM) added the backslash to allow paths to be typed into the command shell while retaining compatibility with MS-DOS 1.0 and CP/M where the slash was the command-line option indicator (i.e. as in typing "dir/w" to give the "wide" option to the "dir" command). Although the command shell was the only part of MS-DOS that required this, the use of backslash in filenames was propagated to most other parts of the user interface. Today, although the underlying operating system supports either character, many Windows programs and sub-systems do not accept the slash as a path delimiter or may misinterpret it if it is used as such. Some programs will only accept forward slashes if the path is placed in double-quotes. Failures of Microsoft security features to recognize unexpected-direction slashes in local and internet paths, while other parts of the operating system still act upon them, have led to some serious lapses in security. Resources that should not be available have been accessed with paths using particular mixes, such as
In the Japanese ISO 646 encoding (a 7-bit code based on ASCII), the code point 0x5C that would be used for backslash in ASCII is instead rendered as a yen mark (¥), while in Korean encoding, it is drawn as a won currency symbol (₩). Computer programs still treat the code as a backslash in these environments, causing confusion. Due to extensive use of the backslash code to represent the yen mark in text, some Unicode fonts like MS Mincho still render the backslash character as a ¥, so the Unicode characters 00A5 (¥) and 005C (\) look identical when these fonts are selected.