问题
Considering the following code (and the fact that VirtualAlloc() returns a void*):
BYTE* pbNext = reinterpret_cast<BYTE*>(
VirtualAlloc(NULL, cbAlloc, MEM_COMMIT, PAGE_READWRITE));
why is reinterpret_cast
chosen instead of static_cast
?
I used to think that reinterpret_cast
is OK for e.g. casting pointers to and from integer types (like e.g. DWORD_PTR
), but to cast from a void*
to a BYTE*
, isn't static_cast
OK?
Are there any (subtle?) differences in this particular case, or are they just both valid pointer casts?
Does the C++ standard have a preference for this case, suggesting a way instead of the other?
回答1:
For convertible pointers to fundamental types both casts have the same meaning; so you are correct that static_cast
is okay.
When converting between some pointer types, it's possible that the specific memory address held in the pointer needs to change.
That's where the two casts differ. static_cast
will make the appropriate adjustment. reinterpret_cast
will not.
For that reason, it's a good general rule to static_cast
between pointer types unless you know that reinterpret_cast
is desired.
回答2:
You should static_cast
. Use static_cast
in cases where you're undoing an implicit conversion.
In this particular case, however, there is no difference because you're converting from void*
. But in general, reinterpret_cast
ing between two object pointers is defined to be (§5.2.10/7):
An object pointer can be explicitly converted to an object pointer of a different type. When a prvalue
v
of type “pointer toT1
” is converted to the type “pointer to cvT2
”, the result isstatic_cast<cv T2*>(static_cast<cv void*>(v))
if bothT1
andT2
are standard-layout types and the alignment requirements ofT2
are no stricter than those ofT1
, or if either type isvoid
. Converting a prvalue of type “pointer toT1
” to the type “pointer toT2
” (whereT1
andT2
are object types and where the alignment requirements ofT2
are no stricter than those ofT1
) and back to its original type yields the original pointer value. The result of any other such pointer conversion is unspecified.
Emphasis mine. Since T1
for you is already void*
, the cast to void*
in reinterpret_cast
does nothing. This is not true in general, which is what Drew Dormann is saying:
#include <iostream>
template <typename T>
void print_pointer(const volatile T* ptr)
{
// this is needed by oversight in the standard
std::cout << static_cast<void*>(const_cast<T*>(ptr)) << std::endl;
}
struct base_a {};
struct base_b {};
struct derived : base_a, base_b {};
int main()
{
derived d;
base_b* b = &d; // implicit cast
// undo implicit cast with static_cast
derived* x = static_cast<derived*>(b);
// reinterpret the value with reinterpret_cast
derived* y = reinterpret_cast<derived*>(b);
print_pointer(&d);
print_pointer(x);
print_pointer(y);
}
Output:
00CBFD5B
00CBFD5B
00CBFD5C
(Note that because y
doesn't actually point to a derived
, using it is undefined behavior.)
Here, reinterpret_cast
comes up with a different value because it goes through void*
. This is why you should use static_cast
when you can, and reinterpret_cast
when you have to.
回答3:
Using static_cast
to cast a pointer to and from void*
is guaranteed to preserve the address.
reinterpret_cast
on the other hand guarantees that if you cast the pointer from one type to other, and back to the original type, the address is preserved.
Although with most implementations, you would see the same results in using either of these, static_cast
should be preferred.
And with C++11
I remember that, using reinterpret_cast
for void*
has a well defined behavior. Before that this behavior was prohibited.
It is not permitted to use reinterpret_cast to convert between pointers to object type and pointers to void.
Proposed resolution (August, 2010):
Change 5.2.10 [expr.reinterpret.cast] paragraph 7 as follows:
An object pointer can be explicitly converted to an object pointer of a different type. When a prvalue v of type “pointer to T1” is converted to the type “pointer to cv T2”, the result is static_cast(static_cast(v)) if both T1 and T2 are standard-layout types (3.9 [basic.types]) and the alignment requirements of T2 are no stricter than those of T1, or if either type is void.
Converting a prvalue of type “pointer to T1” to the type “pointer to T2” (where T1 and T2 are object types and where the alignment requirements of T2 are no stricter than those of T1) and back to its original type yields the original pointer value. The result of any other such pointer conversion is unspecified.
More info here.
Thanks to Jesse Good for the link.
来源:https://stackoverflow.com/questions/15578935/proper-way-of-casting-pointer-types