StringCbPrintf (Windows CE 5.0)

Send Feedback

Developing an Application > Safe String Functions > Safe String Reference > StrSafe.h Byte-Count Functions

This function is a replacement for sprintf. It accepts a format string and a list of arguments, combines them, and returns a formatted string.

The size, in bytes, of the destination buffer is provided to the function to ensure that StringCbPrintf does not write past the end of this buffer.

HRESULT StringCbPrintf(          LPTSTR pszDest,
    size_t cbDest,
    LPCTSTR pszFormat,
     ...
);

Parameters

  • pszDest
    [out] Pointer to a buffer that receives the formatted, null-terminated string created from pszFormat and its arguments.

  • cbDest
    [in] Size of the destination buffer, in bytes.

    This value must be sufficiently large to accommodate the final formatted string plus the terminating null character.

    The maximum number of bytes allowed is STRSAFE_MAX_CCH * sizeof(TCHAR).

  • pszFormat
    [in] Pointer to a buffer containing a printf-style format string.

    This string must be null-terminated.

  • ...
    [in] Arguments to be inserted into pszFormat.

Return Value

This function returns an HRESULT, as opposed to sprintf, which returns the number of bytes stored in its destination buffer.

It is strongly recommended that you use the SUCCEEDED and FAILED macros to test the return value of this function.

Value Description
S_OK There was sufficient space for the result to be copied to pszDest without truncation, and the buffer is null-terminated.
STRSAFE_E_INVALID_PARAMETER The value in cbDest is 0 or larger than STRSAFE_MAX_CCH * sizeof(TCHAR).
STRSAFE_E_INSUFFICIENT_BUFFER The copy operation failed due to insufficient buffer space.

The destination buffer contains a truncated, null-terminated version of the intended result.

Where truncation is acceptable, this is not necessarily a failure condition.

Remarks

StringCbPrintf provides additional processing for proper buffer handling in your code.

Poor buffer handling is implicated in many security issues that involve buffer overruns. StringCbPrintf always null-terminates a nonzero-length destination buffer.

StringCbPrintf can be used in its generic form, or specifically as StringCbPrintfA (for ANSI strings) or StringCbPrintfW (for Unicode strings). The form to use is determined by your data.

String data type String literal Function
char "string" StringCbPrintfA
TCHAR TEXT("string") StringCbPrintf
WCHAR L"string" StringCbPrintfW

StringCbPrintf and its ANSI and Unicode variants are replacements for these functions:

If the strings pointed to by pszDest, pszFormat, or any argument strings overlap, behavior is undefined.

Neither pszFormat nor pszDest should be NULL.

If you need the handling of null string pointer values, see StringCbPrintfEx.

Example

The following code example shows a basic use of StringCbPrintf, using four arguments.

int const arraysize = 30;
TCHAR pszDest[arraysize]; 
size_t cbDest = arraysize * sizeof(TCHAR);

LPCTSTR pszFormat = TEXT("%s %d + %d = %d.");
TCHAR* pszTxt = TEXT("The answer is");

HRESULT hr = StringCbPrintf(pszDest, cbDest, pszFormat, pszTxt, 1, 2, 3);

// The resultant string at pszDest is "The answer is 1 + 2 = 3."

Requirements

OS Versions: Windows CE 5.0 and later.
Header: strsafe.h.
Link Library: strsafe.lib.

See Also

StringCchPrintf | StringCbPrintfEx | StringCbVPrintf

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.