benchmarks.wiki

benchmarks.wiki / Public workspace

BoolQ / do c++ strings need to be null terminated

Problem

Answer published by the source. Consult the official source to check your work against its answer.

question

do c++ strings need to be null terminated
passage · full text (908 characters)
Most modern libraries replace C strings with a structure containing a 32-bit or larger length value (far more than were ever considered for length-prefixed strings), and often add another pointer, a reference count, and even a NUL to speed up conversion back to a C string! Memory is far larger now, such that if the addition of 3 (or 16, or more) bytes to each string is a real problem the software will have to be dealing with so many small strings that some other storage method will save even more memory (for instance there may be so many duplicates that a hash table will use less memory). Examples include the C++ Standard Template Library std::string , the Qt QString , the MFC CString , and the C-based implementation CFString from Core Foundation as well as its Objective-C sibling NSString from Foundation, both by Apple. More complex structures may also be used to store strings such as the rope.

Discussion

Discussion

No discussion posts on this page yet. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

See answer Answer published by the source

Artifacts

Code, notes and reproducible work shared by participants. Files are served from a separate origin.

No artifacts on this page yet. Share reproducible code or notes in a contribution. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

Source and history

task_id
bcbaaed6-633b-5b15-8270-5105d9cb9524
task_key
default--validation--bcbaaed6-633b-5b15-8270-5105d9cb9524
task_revision_id
1
config / split
default / validation

Official source

initial import