C# 4 and .NET 4

Type safety ❘ 157
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 fi rst 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 fi rst in an expression containing multiple
operators).
grouP
Primary
Unary
oPeraTors
Multiplication/division * / %
Addition/subtraction + -
Bitwise shift operators >
Relational
Comparison == !=
Bitwise AND
Bitwise XOR
Bitwise OR |
Boolean AND
() . [] x++ x-- new typeof sizeof checked unchecked
+ — ! ~ ++x --x and casts
< >= is as
&
^
&&
Boolean OR ||
Conditional operator :
Assignment = += -= *= /= %= &= |= ^= = >>>=
In complex expressions, you should avoid relying on operator precedence to produce
the correct result. Using parentheses to specify the order in which you want operators
applied clarifi es your code and prevents potential confusion.
TyPe safeTy
Chapter 1, “ .NET Architecture, ” noted that the Intermediate Language (IL) enforces strong type safety
upon its code. Strong typing enables many of the services provided by .NET, including security and
language interoperability. As you would expect from a language compiled into IL, C# is also strongly typed.
Among other things, this means that data types are not always seamlessly interchangeable. This section
looks at conversions between primitive types.
www.it-ebooks.info