Wolfram Research, Inc.
A.2.7 Operator Input Forms
Characters that are not letters, letter-like forms or structural elements are treated by Mathematica as operators. Mathematica has built-in rules for interpreting all operators. The functions to which these operators correspond may or may not, however, have built-in evaluation or other rules. Cases in which built-in meanings are by default defined are indicated by in the tables below.
Operators that construct two-dimensional boxes—all of which have names beginning with back-slash—can only be used inside \( ... \). The table below gives the interpretations of these operators within \!\( ... \). Section A.2.9 gives interpretations when no \! is included.
Objects used in the tables of operator input forms.
Operator input forms, in order of decreasing precedence, part one.
Operator input forms, in order of decreasing precedence, part two.
Operator input forms, in order of decreasing precedence, part three.
Operator input forms, in order of decreasing precedence, part four.
Operator input forms, in order of decreasing precedence, part five.
Operator input forms, in order of decreasing precedence, part six.
Additional input forms, in order of decreasing precedence.
Special characters that appear in operators usually have names that correspond to the names of the functions they represent. Thus the character has name \[CirclePlus] and yields the function CirclePlus. Exceptions are \[GreaterSlantEqual], \[LessSlantEqual] and \[RoundImplies].
The delimiters in matchfix operators have names \[LeftName] and \[RightName].
Section A.12.1 gives a complete listing of special characters that appear in operators.
Keyboard and special characters with the same interpretations.
Some keyboard and special characters with different interpretations.
Precedence and the Ordering of Input Forms
The tables of input forms are arranged in decreasing order of precedence. Input forms in the same box have the same precedence. Each page in the table begins a new box. As discussed in Section 2.1.3, precedence determines how Mathematica groups terms in input expressions. The general rule is that if has higher precedence than , then is interpreted as , and is interpreted as .
Grouping of Input Forms
The third columns in the tables show how multiple occurrences of a single input form, or of several input forms with the same precedence, are grouped. For example, a/b/c is grouped as (a/b)/c ("left associative"), while a^b^c is grouped as a^(b^c) ("right associative"). No grouping is needed in an expression like a + b + c, since Plus is fully associative, as represented by the attribute Flat.
Precedence of Integration Operators
Forms such as have an "outer" precedence just below Power, as indicated in the table above, but an "inner" precedence just above . The outer precedence determines when needs to be parenthesized; the inner precedence determines when needs to be parenthesized.
\[ContourIntegral], \[ClockwiseContourIntegral] and \[DoubleContourIntegral] work the same as \[Integral].
See Section A.2.8 for two-dimensional input forms associated with integration operators.
Spaces and Multiplication
Spaces in Mathematica denote multiplication, just as they do in standard mathematical notation. In addition, Mathematica takes complete expressions that are adjacent, not necessarily separated by spaces, to be multiplied together.
Alternative forms for multiplication.
An expression like x!y could potentially mean either (x!)*y or x*(!y). The first interpretation is chosen because Factorial has higher precedence than Not.
Spaces within single input forms are ignored. Thus, for example, a + b is equivalent to a+b. You will often want to insert spaces around lower precedence operators to improve readability.
You can give a "coefficient" for a symbol by preceding it with any sequence of digits. When you use numbers in bases larger than 10, the digits can include letters. (In bases other than 10, there must be a space between the end of the coefficient, and the beginning of the symbol name.)
Some cases to be careful about.
Spaces to Avoid
You should avoid inserting any spaces between the different characters in composite operators such as /., =. and >=. Although in some cases such spaces are allowed, they are liable to lead to confusion.
Another case where spaces must be avoided is between the characters of the pattern object x_. If you type x _, Mathematica will interpret this as x*_, rather than the single named pattern object x_.
Similarly, you should not insert any spaces inside pattern objects like x_:value.
Spacing characters equivalent to an ordinary keyboard space.
Relational operators can be mixed. An expression like a > b >= c is converted to Inequality[a, Greater, b, GreaterEqual, c], which effectively evaluates as (a > b) && (b >= c). (The reason for the intermediate Inequality form is that it prevents objects from being evaluated twice when input like a > b >= c is processed.)
Any file name can be given in quotes after <<, >> and >>>. File names can also be given without quotes if they contain only alphanumeric characters, special characters and the characters `, /, ., \, !, -, _, :, $, *, ~ and ?, together with matched pairs of square brackets enclosing any characters other than spaces, tabs and newlines. Note that file names given without quotes can be followed only by spaces, tabs or newlines, or by the characters ), ], as well as semicolon and comma.