12-16-2016, 09:39 AM
Hi gintaras, hi all
Gintaras, i mess with some lpstr functions (my fault, not QM one of course)
The problem is that the lpstr seems not be reinitialized correctly in my code.
I'm aware that a lpstr can be set to null by lpstr s=0, but it seems to be an issue in new OS's about "nullification" (nullptr comes to mind, and seems not yet implemented in QM)
The general code i use for that is to declare an unitialized lpstr and make the used one equal it.
lpstr s="some text"
lpstr f
//code
....
//code
s=f
Is there a better way?
2.
str f.lpstr="some text"
is using this as fast as using a general lpstr? I ask that because using pointers is usually more efficient than direct str manipulation.
Thanks for your patience !!
Gintaras, i mess with some lpstr functions (my fault, not QM one of course)
The problem is that the lpstr seems not be reinitialized correctly in my code.
I'm aware that a lpstr can be set to null by lpstr s=0, but it seems to be an issue in new OS's about "nullification" (nullptr comes to mind, and seems not yet implemented in QM)
The general code i use for that is to declare an unitialized lpstr and make the used one equal it.
lpstr s="some text"
lpstr f
//code
....
//code
s=f
Is there a better way?
2.
str f.lpstr="some text"
is using this as fast as using a general lpstr? I ask that because using pointers is usually more efficient than direct str manipulation.
Thanks for your patience !!