1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[docs] qvsnprint(): mention %a and %ls differences on WASM/Android

Browse Source 
Pick-to: 6.7 6.5 6.2
Task-number: QTBUG-127110
Change-Id: I919170881846f3a08890ac0a8accfb859157d193
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
(cherry picked from commit 1aedd4d7c9968054a1c2880000a5007bb826a179)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Marc Mutz 2024-07-18 11:22:26 +02:00 committed by Qt Cherry-pick Bot
parent 6c21f8103b
commit c3477a7375
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/corelib/text/qvsnprintf.cpp
View File

@ -30,7 +30,9 @@ QT_BEGIN_NAMESPACE
\warning Since vsnprintf() shows different behavior on certain \warning Since vsnprintf() shows different behavior on certain
platforms, you should not rely on the return value or on the fact platforms, you should not rely on the return value or on the fact
that you will always get a 0 terminated string back. that you will always get a 0 terminated string back. There are also
differences in how \c{%a} (hex floats) and \c{%ls} (wide strings) are
handled on WebAssembly and Android.
Ideally, you should never call this function but use QString::asprintf() Ideally, you should never call this function but use QString::asprintf()
instead. instead.