summaryrefslogtreecommitdiffstats
path: root/src/corelib/io/qprocess.cpp
diff options
context:
space:
mode:
authorEdward Welbourne <edward.welbourne@qt.io>2020-06-04 19:24:41 +0200
committerEdward Welbourne <edward.welbourne@qt.io>2020-06-05 12:13:29 +0200
commit8a95404905026a7d2caa507b49ce23e04148d4af (patch)
tree307f83516207fdd03e2671f81d157d4998726605 /src/corelib/io/qprocess.cpp
parentc5f22d1c14a551881a2360c7974a55f6e60f8f7b (diff)
Clean out string/character mentions from QByteArray docs
In some places QByteArray does interpret bytes as characters and a sequence of them as a text string; everywhere else, however, it now refers to them as bytes. Add a section to the class doc explaining how char* pointers are interpreted; the handling of '\0'-termination is surely familiar to most readers, but making it explicit provides contrast for the explanation of there being no such special treatment of '\0' bytes when a stard address and length are given. Also mention in the class doc that interaction with QString is done via UTF-8 encoding and can be avoided by defining a macro. Shorten, in light of that, the description of that encoding where it appears in affected methods. In the process, clean up lots of phrasings. Change-Id: Ic97dce4a20752e277eeab35a06737322b2074692 Reviewed-by: Lars Knoll <lars.knoll@qt.io>
Diffstat (limited to 'src/corelib/io/qprocess.cpp')
0 files changed, 0 insertions, 0 deletions