Operator Shortcuts

The following table shows the full list of shortcut assignment operators available in C#.

Open table as spreadsheet

Shortcut Operator	Equivalent To
x + +, + + x	x = x + 1
x - -, - - x	x = x – 1
x + = y	x = x + y
x –= y	x = x – y
x *= y	x = x * y
x / = y	x = x / y
x % = y	x = x % y
x > > = y	x = x > > y
x < < = y	x = x < < y
x & = y	x = x & y
x | = y	x = x | y
x ^ = y	x = x ^ y

You may be wondering why there are two examples each for the ++ increment and the -- decrement operators. Placing the operator before the expression is known as a prefix, and placing the operator after the expression is known as a postfix, and there is a difference in the way they behave.

The increment and decrement operators can act both as whole expressions and within expressions. When used by themselves the effect of both the prefix and postfix versions is identical and corresponds to the statement x = x + 1. When used within larger expressions, the prefix operator will increment the value of x before the expression is evaluated; in other words, x is incremented and the new value is used in the expression. In contrast, the postfix operator increments the value of x after the expression is evaluated - the expression is evaluated using the original value of x. The following example uses the increment operator (++) as an example to demonstrate the difference between the prefix and postfix behavior:

int x = 5;
if (++x == 6)
{
   Console.WriteLine("This will execute");
}
if (x++ == 7)
{
   Console.WriteLine("This won't");
}

The first if condition evaluates to true, because x is incremented from 5 to 6 before the expression is evaluated. The condition in the second if statement is false, however, because x is incremented to 7 only after the entire expression has been evaluated (while x = 6).

The prefix and postfix operators --x and x-- behave in the same way, but decrement rather than increment the operand.

The other shortcut operators, such as += and -=, require two operands, and are used to modify the value of the first operand by performing an arithmetic, logical, or bitwise operation on it. For example, the next two lines are equivalent:

x += 5;
x = x + 5;

The Ternary Operator

The ternary operator (?:) is a shorthand form of the if...else construction. It gets its name from the fact that it involves three operands. It allows you to evaluate a condition, returning one value if that condition is true, or another value if it is false. The syntax is:

condition ? true_value : false_value

Here, condition is the Boolean expression to be evaluated, true_value is the value that will be returned if condition is true, and false_value is the value that will be returned otherwise.

When used sparingly, the ternary operator can add a dash of terseness to your programs. It is especially handy for providing one of a couple of arguments to a function that is being invoked. You can use it to quickly convert a Boolean value to a string value of true or false. It is also handy for displaying the correct singular or plural form of a word, for example:

int x = 1;
string s = x.ToString() + " ";
s += (x == 1 ? "man" : "men");
Console.WriteLine(s);

This code displays 1 man if x is equal to one but will display the correct plural form for any other number. Note, however, that if your output needs to be localized to different languages, you will have to write more sophisticated routines to take account of the different grammatical rules of different languages.

The checked and unchecked Operators

Consider the following code:

byte b = 255;
b++;
Console.WriteLine(b.ToString());

The byte data type can only hold values in the range zero to 255, so incrementing the value of b causes an overflow. How the CLR handles this depends on a number of issues, including compiler options, so whenever there’s a risk of an unintentional overflow, you need some way of making sure that you get the result you want.

To do this, C# provides the checked and unchecked operators. If you mark a block of code as checked, the CLR will enforce overflow checking, and throw an OverflowException if an overflow occurs. Let’s change the code to include the checked operator:

byte b = 255;
checked
{
   b++;
}
Console.WriteLine(b.ToString());

When you try to run this code, you will get an error message like this:

Unhandled Exception: System.OverflowException: Arithmetic operation resulted in an
overflow.
   at Wrox.ProCSharp.Basics.OverflowTest.Main(String[] args)

If you want to suppress overflow checking, you can mark the code as unchecked:

byte b = 255;unchecked
{   b++;
}
Console.WriteLine(b.ToString());

In this case, no exception will be raised, but you will lose data - because the byte type can’t hold a value of 256, the overflowing bits will be discarded, and your b variable will hold a value of zero.

Note that unchecked is the default behavior. The only time you are likely to need to explicitly use the unchecked keyword is if you need a few unchecked lines of code inside a larger block that you have explicitly marked as checked.

The is Operator

The is operator allows you to check whether an object is compatible with a specific type. For example, to check whether a variable is compatible with the object type:

int i = 10;
if (i is object)
{
   Console.WriteLine("i is an object");
}

int, like all C# data types, inherits from object; therefore the expression i is object will evaluate to true in this case, and the appropriate message will be displayed.

The as Operator

The as operator is used to perform explicit type conversions of reference types. If the type being converted is compatible with the specified type, conversion is performed successfully. However, if the types are incompatible, the as operator returns the value null. As shown in the following code, attempting to convert an object reference to a string will return null if the object reference does not actually refer to a string instance:

object o1 = "Some String";
object o2 = 5;

string s1 = o1 as string;   // s1 = "Some String"
string s2 = o2 as string;   // s2 = null

The as operator allows you to perform a safe type conversion in a single step without the need to first test the type using the is operator and then perform the conversion.

The sizeof Operator

You can determine the size (in bytes) required on the stack by a value type using the sizeof operator:

unsafe
{
   Console.WriteLine(sizeof(int));
}

This will display the number 4, because an int is 4 bytes long.

Notice that you can only use the sizeof operator in unsafe code. Chapter 11 looks at unsafe code in more detail.

The typeof Operator

The typeof operator returns a System.Type object representing a specified type. For example, typeof(string) will return a Type object representing the System.String type. This is useful when you want to use reflection to find out information about an object dynamically. Chapter 12, “Reflection,” looks at reflection.

Nullable Types and Operators

Looking at the Boolean type, you have a true or false value that you can assign to this type. Though, what if you wanted to define the value of the type as undefined? This is where using nullable types can have a distinct value to your applications. If you use nullable types in your programs, you must always consider the effect a null value can have when used in conjunction with the various operators. Usually, when using a unary or binary operator with nullable types, the result will be null if one or both of the operands is null. For example:

int? a = null;

int? b = a + 4;      // b = null
int? c = a * 5;      // c = null

However, when comparing nullable types, if only one of the operands is null, the comparison will always equate to false. This means that you cannot assume a condition is true just because its opposite is false, as often happens in programs using non-nullable types. For example:

int? a = null;
int? b = -5;

if (a >= b)
   Console.WriteLine("a >= b");
else
   Console.WriteLine("a < b");

The Null Coalescing Operator

The null coalescing operator (??) provides a shorthand mechanism to cater to the possibility of null values when working with nullable and reference types. The operator is placed between two operands - the first operand must be a nullable type or reference type, and the second operand must be of the same type as the first or of a type that is implicitly convertible to the type of the first operand. The null coalescing operator evaluates as follows: if the first operand is not null, then the overall expression has the value of the first operand. However, if the first operand is null, the overall expression has the value of the second operand. For example:

int? a = null;
int b;

b = a ?? 10;     // b has the value 10
a = 3;
b = a ?? 10;     // b has the value 3

If the second operand cannot be implicitly converted to the type of the first operand, a compile-time error is generated.

Operator Precedence

The following table shows the order of precedence of the C# operators. The operators at the top of the table are those with the highest precedence (that is, the ones evaluated first in an expression containing multiple operators).

Open table as spreadsheet

Group	Operators
Primary	() . [] x++ x-- new typeof sizeof checked unchecked
Unary	+ - ! ~ + + x --x and casts
Multiplication/division	* / %
Addition/subtraction	+ –
Bitwise shift operators	<< >>
Relational	< > <= >= is as
Comparison	= = ! =
Bitwise AND	&
Bitwise XOR	^
Bitwise OR	|
Boolean AND	&&
Boolean OR	| |
Ternary operator	? :
Assignment	= + = – = * = / = % = & = | = ^ = << = >> = >>> =