In computer science, a cast, or explicit type conversion, is a special programming instuction which specifies what data type to treat a variable as (or an intermediate calculation result) in a given expression.
Each programming language has its own rules on how types can be casted. In general, both objects and fundamental data types can be casted. Casting will ignore "extra" information (but never adds information to the type being casted).
As an example with fundamental data types, a fixed-point float could be cast as an integer, where the data beyond the decimal (or binary) point is ignored. Alternatively, an integer could be cast as a float if, for example, a function call required a floating point type (but, as noted, no information is really added - 1 would become 1.0000000).
Object casting works in a similar way. A subclass can be cast as a parent type, where the "extra" information that makes it a subclass is ignored, and only the parts inherited from the parent are treated. For example, a triangle class derived from a shape class could be cast as a shape.
Static casts converts type-compatible values. For instance the following:
double myDouble = 3.0;
int myInt = static_cast(myDouble);
converts the double-precision floating point value myDouble (3.0) to the corresponding integral value (3).
Static casts can be dangerous:
YourClass * pYour = GimmeAnObject();
void * pv = pYour; // no cast needed.
MyClass * p = static_cast(pYour); // MyClass had better be related to YourClass...
p->SomeMethod(); // ...or this might blow up in a nasty way.
Static casts on pointers or references don't verify that the pointed-to object is type-compatible to the
new type.
A dynamic cast is safer than a static cast in this scenario: it is compiled by the compiler into a call to the C++ runtime library where a check is made to ensure legal casts. This is analogous to the casts in Java.
YourClass * pYour = GimmeAnObject();
void * pv = pYour; // no cast needed.
MyClass * p = dynamic_cast(pYour); // This won't blow up in the same way
if (p != 0)
p->SomeMethod(); // C++ guarantees p points to a MyClass
Dynamic casts on pointer return a null pointer if cast value is type incompatible. Dynamic casts on a reference throw an type exception.
A const cast casts away the 'constness' of an object, returning a non-const reference to the same. This allows modifications to objects that normally would be treated read-only by the compiler:
const MyClass * cantTouchThis = CreateConstObject();
cantTouchThis->constant_value = 41; // compile-time error.
const_cast(cantChangeThis)->constant_value = 42; // compiles, but who knows what happens at runtime?
The reinterpret cast is the most notorious one in C++. It allows the reinterpretation of the raw bit
pattern of the value to be cast, disregarding the type system completely. For example, it allows the casting
of an arbitrary integer to a pointer to an object:
MyClass * pclass = reinterpret_cast(0xDEADBEEF); // I'm an 733+ h@x0r and know what I'm doing.
pclass->some_field = 3.14159; // very unsafe indeed
Opinions were divided when these verbose casts were introduced into the language. Detractors argued the new syntax was 'ugly', while supporters claimed that since casting is such an 'ugly' activity to begin with, it should be highlit with an 'ugly' syntax to alert programmers. Another perceived advantage is the ease with which verbose casts can be located in source code using programming tools like grep.
