can not print correctly after convert QString to char *
-
@Christian-Ehrlicher
Thank you very much, and thank other replyer.
I think i understand your reply, and I do fogot the temp object , maybe because I also use java a lot.and i alse have a few questions:
- where is the temp object in memory, stack or heap or somewhere else.
- if it is on stack, it can not remain until the stack is finished
@Mozzie said in can not print correctly after convert QString to char *:
where is the temp object in memory, stack or heap or somewhere else.
It's on the stack since you did not allocate it with new
if it is on stack, it can not remain until the stack is finished
No, this is not allowed since it's unnamed.
It's also not c++ specific - you can do the same (in a little bit more obvious way) in C:
int *myPtr = nullptr; { int a = 3; myPtr = &a; printf("%d\n", *myPtr); // works fine } printf("%d\n", *myPtr); // works on garbage and may eat kitten
-
@Mozzie said in can not print correctly after convert QString to char *:
where is the temp object in memory, stack or heap or somewhere else.
It's on the stack since you did not allocate it with new
if it is on stack, it can not remain until the stack is finished
No, this is not allowed since it's unnamed.
It's also not c++ specific - you can do the same (in a little bit more obvious way) in C:
int *myPtr = nullptr; { int a = 3; myPtr = &a; printf("%d\n", *myPtr); // works fine } printf("%d\n", *myPtr); // works on garbage and may eat kitten
@Christian-Ehrlicher said in can not print correctly after convert QString to char *:
int *myPtr = nullptr;
Never heard of
nullptr
in C ;-)NULL
was much nicer to read anyway. -
@aha_1980
Wow, OK, yes, I need to read! My problem is I have been "spoiled" by using C# and then Python/PyQt/PySide2 for so long now that I rarely have to think about this!So let's take a basic, if my C++ holds up. If I write a function
QByteArray func() { QByteArray qb; return qb; }
does that return such a "temporary object"? And that would be true for any class/struct I decalred and then returned in that fashion?
This post is deleted! -
@Mozzie said in can not print correctly after convert QString to char *:
where is the temp object in memory, stack or heap or somewhere else.
It's on the stack since you did not allocate it with new
if it is on stack, it can not remain until the stack is finished
No, this is not allowed since it's unnamed.
It's also not c++ specific - you can do the same (in a little bit more obvious way) in C:
int *myPtr = nullptr; { int a = 3; myPtr = &a; printf("%d\n", *myPtr); // works fine } printf("%d\n", *myPtr); // works on garbage and may eat kitten
@Christian-Ehrlicher
thanks, it helped a lot.
and i have a hunch{//main stack QString s = "hello world"; char* p = nullptr; {// toUtf8() QByteArray b = s.toUtf8(); {// data(); p = b.data(); qDebug() << p; // does this is same as "qDebug() << s.toUtf8().data();" } } // b is freed qDebug() << p; // this is same as "char * p = s.toUtf8().data(); qDebug() << p;" }
does this right?
-
@Christian-Ehrlicher said in can not print correctly after convert QString to char *:
int *myPtr = nullptr;
Never heard of
nullptr
in C ;-)NULL
was much nicer to read anyway.@JonB
nullptr is a c++11 key word, you can still use NULL, but NULL is defined as 0, sometimes it may cause some problem.such as:
void test(int *p) { qDebug() << "int *"; } void test(int i) { qDebug() << "int"; } test(NULL); test(nullptr);
output
int int *
-
@JonB
nullptr is a c++11 key word, you can still use NULL, but NULL is defined as 0, sometimes it may cause some problem.such as:
void test(int *p) { qDebug() << "int *"; } void test(int i) { qDebug() << "int"; } test(NULL); test(nullptr);
output
int int *
-
@Christian-Ehrlicher
thanks, it helped a lot.
and i have a hunch{//main stack QString s = "hello world"; char* p = nullptr; {// toUtf8() QByteArray b = s.toUtf8(); {// data(); p = b.data(); qDebug() << p; // does this is same as "qDebug() << s.toUtf8().data();" } } // b is freed qDebug() << p; // this is same as "char * p = s.toUtf8().data(); qDebug() << p;" }
does this right?
@Mozzie said in can not print correctly after convert QString to char *:
does this right?
Yes, exactly.
-
@Mozzie said in can not print correctly after convert QString to char *:
does this right?
Yes, exactly.
@Christian-Ehrlicher
thanks.