Creates a CFMutableString object whose Unicode character buffer is controlled externally.
- iOS 2.0+
- macOS 10.0+
- Mac Catalyst 13.0+
- tvOS 9.0+
- watchOS 2.0+
- Core Foundation
The allocator to use to allocate memory for the string. Pass
kto use the current default allocator.
The Unicode character buffer for the new
CFMutable. Before calling, create this buffer on the stack or heap and optionally initialize it with Unicode character data. Upon return, the created
CFStringobject keeps its own copy of the pointer to this buffer. You may pass in
NULLif there is no initial buffer being provided.
The number of characters initially in the Unicode buffer pointed to by
The capacity of the external buffer (
chars); that is, the maximum number of Unicode characters that can be stored. This value should be
0if no initial buffer is provided.
The allocator to use to reallocate the external buffer when editing takes place and for deallocating the buffer when string is deallocated. If the default allocator is suitable for these purposes, pass
NULL. To manage the buffer yourself, pass
A new mutable string, or
NULL if there was a problem creating the object. Ownership follows the The Create Rule.
This function permits you to create a
CFMutable object whose backing store is an external Unicode character buffer—that is, a buffer that you control (or can control) entirely. This function allows you to take advantage of the features of
CFString, particularly the
CFMutable functions that add and modify character data. But at the same time you can directly add, delete, modify, and examine the characters in the buffer. You can even replace the buffer entirely. If, however, you directly modify or replace the character buffer, you should inform the
CFString object of this change with the
If you mutate the character contents with the
CFString functions, and the buffer needs to be enlarged, the
CFString object calls the allocation callbacks specified for the allocator
the default allocator
k is specified.
This function should be used in special circumstances where you want to create a
CFString wrapper around an existing, potentially large
Uni buffer you own. Using this function causes the
CFString object to forgo some of its internal optimizations, so it should be avoided in general use. That is, if you want to create a
CFString object from a small
Uni buffer, and you don't need to continue owning the buffer, use one of the other creation functions (for instance