https://bugs.kde.org/show_bug.cgi?id=428078

--- Comment #2 from Marcel Bosling <marcel.bosl...@rwth-aachen.de> ---
Hi Jan,

indeed the <QDebug> statement is a leftover of my investigations.

These are the results when using auto and QByteArray for buf:

const QString &sername:  "someexampleusern...@whereever.org"
auto buf:  "a\x00u\x00t\x00o\x00 \x00""b\r\n"
QByteArray buf:  "c29tZWV4YW1wbGV1c2VybmFtZUB3aGVyZWV2ZXIub3Jn\r\n"



SIDENOTE:


I've tried to reproduce the problem with a simple QT program doing just the
conversion with auto and QByteArray. The resulting variables hold the same
(correct) base64 encoded data, yielding:

auto:  "U29tZWxvbmd1c2VybmFtZUB3aGVyZWV2ZXIub3Jn\r\n"
bufQB:  "U29tZWxvbmd1c2VybmFtZUB3aGVyZWV2ZXIub3Jn\r\n"


SOURCE:

#include <QCoreApplication>
#include <QDebug>

int main(int argc, char *argv[])
{
    QCoreApplication a(argc, argv);

    const QString username = "somelongusern...@whereever.org";

    const QString &reftousername = username;

    auto bufAuto = reftousername.toUtf8().toBase64() + "\r\n";
    QByteArray bufQB = reftousername.toUtf8().toBase64() + "\r\n";

    qDebug()<<"auto: " << bufAuto;
    qDebug()<<"bufQB: " << bufQB;

    return a.exec();
}

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to