<![CDATA[Why is QString(char*) private in trunk?]]>In qstring.h these methods are now private, I checked the qt5 trunk out from git:

private:
#if defined(QT_NO_CAST_FROM_ASCII)
QString &operator+=(const char *s);
QString &operator+=(const QByteArray &s);
QString(const char *ch);
QString(const QByteArray &a);
QString &operator=(const char *ch);
QString &operator=(const QByteArray &a);
#endif

Why? This is going to make a lot of code uglier, I now have to wrap every single function call where I used to be able to say "string.split("HI")" with "string.split(QString.fromUtf8("HI")"

]]>https://forum.qt.io/topic/46669/why-is-qstring-char-private-in-trunkRSS for NodeWed, 09 Sep 2026 09:51:33 GMTSat, 04 Oct 2014 18:19:25 GMT60<![CDATA[Reply to Why is QString(char*) private in trunk? on Sun, 05 Oct 2014 06:49:52 GMT]]>There are different approaches to making something multilingual, in any case I would rather have the option of coding as fast as possible and worry about business decisions at a point of time of my choosing.

]]>https://forum.qt.io/post/246267https://forum.qt.io/post/246267Sun, 05 Oct 2014 06:49:52 GMT<![CDATA[Reply to Why is QString(char*) private in trunk? on Sat, 04 Oct 2014 22:34:20 GMT]]>Hi, also you can use
@
string.split(tr("Hi"));
@

it's useful in those environments where QString(char*) is private 100% of the time, for example when you're writing a Qt Creator plugin.

As SGaist suggests, it's a good idea always to put your hardcoded strings inside a function anyway, because maybe your product is a success and you have to translate it to another language!

]]>https://forum.qt.io/post/246257https://forum.qt.io/post/246257Sat, 04 Oct 2014 22:34:20 GMT<![CDATA[Reply to Why is QString(char*) private in trunk? on Sat, 04 Oct 2014 20:02:38 GMT]]>Hi,

Look upper in the header file under the "// ASCII compatibility" comment, you'll see that if you don't define QT_NO_CAST_FROM_ASCII the methods are public.

As for the rest you would rather use:

@string.split(QLatin1String("Hi"));@

The reasoning behind is explained in the documentation of QString and QLatin1String

]]>https://forum.qt.io/post/246238https://forum.qt.io/post/246238Sat, 04 Oct 2014 20:02:38 GMT