Is there a way to make output from QCryptographicHash readable QByteArray?
-
IT WORKS!
Thank you!@Christian-Ehrlicher That works, of course. But outside of the example it looks like this:
I wrapped all those hash-generating bits into a small class. For convenience, I have there:private: QRandomGenerator generator; QCryptographicHash *hash;
In the constructor I init the generator and the hash. So I have
hash = new QCryptographicHash(QCryptographicHash::Sha512);
that is later deleted in the destructor. It apparently is a weak day for me but I failed to find a way of this private member NOT to be on the heap.EDIT:
@JonB I saw your comment :)
I understood, just at this hour I am not entirely online, just from time to time :) -
@artwaw
Personally I don't worry about heap vs stack as some others do, when I did Python it's all heap anyway. And sometimes I heap to avoid include dependencies in header files.But why can't you have
QCryptographicHash hash(QCryptographicHash::Sha512);
as the member variable instead of pointer? -
@artwaw
Ah! That will be because you are in the "sometimes I heap to avoid include dependencies in header files" I mentioned :)Intentionally or not, in your
.h
file you have preceded this line withclass QCryptographicHash;
That allows
QCryptographicHash *
declarations to the incomplete type.You will need
#include <QCryptographicHash>
to make the declaration acceptable. If that is what you wish to do.
I see for example you alreday have
QRandomGenerator generator;
so you have chosen to do that one with include.
-
@artwaw said in Is there a way to make output from QCryptographicHash readable QByteArray?:
I get instant
/Users/(username)/cpp/512hash/cryptoclass/cryptoclass.h:24: error: no type named 'Sha512' in 'QCryptographicHash'
Then I have no idea why you get a "no type" error for
QCryptographicHash hash(QCryptographicHash::Sha512);
in a
.h
but not in a.cpp
or whyhash = new QCryptographicHash(QCryptographicHash::Sha512);
is acceptable.