[Solved]Dynamic cast to void pointer
-
For the sake of clarity, try separating the call to QAxBase::dynamicCall() from the call to QVariant::value(). Then verify that the QVariant is valid, at least for development purposes. Finally, cast it to a void pointer, and inspect it again.
QAxBase::dynamicCall() is documented as returning an invalid QVariant if the call fails, or if the called method doesn't return a value. Maybe something is going wrong prior to the cast.
-
Hi jeremy_k
I have verified that QVariant is valid. qDebug prints this,
QVariant(int, 419171632).that means dynamic call is working, there is issue with casting.
So, i have a QVariant and i want to convert it to void *.
I am doing
@
HANDLE hBlock = QVariant.value<void *>;
@
where QVariant is QVariant(int, 419171632)
i get 0x0 in hBlock. -
Try a reinterpret_cast<void *>
@#include <cstdio>
#include <QVariant>int main(int argc, char *argv[])
{
QVariant var(0x12345678);
void * ptr1 = var.value<void *>();
void * ptr2 = reinterpret_cast<void *>(var.value<int>());
printf("%p %p\n", ptr1, ptr2);
return 0;
}@ -
Sorry about the 5 thing, I missed a parenthesis when I was reading the code. :)
Glad the reinterpret_cast worked for you though.
-
Hi, ambershark
You should not sorry for that , actually i should sorry for posting some unreadable code.-
reinterpret_cast worked for me, but yesterday i was reading about it and found that its dangerous to use.
-
If using QVariant.value<>() is a correct way to convert QVariant to any other type then why it is not working in my case?
-
On many forums its recommended not to use reinterpret_cast, then what might be the other way in this case(QVariant to void *)?
-
-
reinterpret_cast tells the compiler "trust me, I know what I'm doing". There is no other options (that I know of) for transforming to or from void *. Nothing inherits from void *, and it doesn't inherit from anything. There is no inherently meaningful way to convert it to a pointer to a valid object without risking converting it into a pointer to an invalid object.
Because of it's lack of meaning, arithmetic and dereferencing void * are also meaningless.
So no, if you don't understand what it is or how it can be used, staying away from both reinterpret_cast and void * is a good idea. The same caveat goes for C-style casting.
-
I was slightly hasty dismissing static_cast<void *>. That works from a pointer to void *, and back again.
More detail: http://www.cplusplus.com/doc/tutorial/typecasting/
-
I agree with what jeremy_k said. I use reinterpret_cast a bit in code. It can be dangerous because it has no type checking. When dealing with void *s though there is rarely any type checking and using reinterpret_cast is just fine. Like jeremy said it is basically telling the compiler you know what is in that data and want it cast to a certain type.
The "dangerous" part comes in if you are not paying attention as a programmer. If you know for sure your pointer is a valid one of class X then a reinterpret_cast is just fine.
If you think of it in C style it is the same as saying:
@
void myVoid = (void)new MyClass;
MyClass *c = (MyClass *)myVoid;
@Both of those above examples are the same as reinterpret_cast's in c++. In fact you can use the C style casting method in C++ just fine.
