mbsntowcs(3)                                               mbsntowcs(3)

  mbstowcs()

  NAME

    mbstowcs(), mbsntowcs() - convert character string to a wide-character
    string

  SYNOPSIS

    #include 

    size_t mbstowcs (wchar_t *pwcs, const char *s, size_t n)
    size_t mbsntowcs (wchar_t *pwcs, const char *s, size_t n, size_t m)

  DESCRIPTION

    The mbstowcs(3) function converts a sequence of characters that begins in
    the initial shift state from the array pointed to by s into a sequence of
    corresponding wide-character codes and stores not more than n wide-
    character codes into the array pointed to by pwcs. No characters following
    a null byte (which is converted into a wide-character code with a value of
    0) will be examined or converted. Each character is converted as if by a
    call to mbtowc(3), except that the shift state of mbtowc(3) is not
    affected.

    No more than n elements will be modified in the array pointed to by pwcs.
    If copying takes place between objects that overlap, the behavior is
    undefined.

    The behavior of this function is affected by the LC_CTYPE category of the
    current locale. If pwcs is a null pointer, mbstowcs(3) returns the length
    required to convert the entire array regardless of the value of n, but no
    values are stored.

    The mbsntowcs(3) function is identical to mbstowcs(3), except that only
    the number of characters specified by the m argument are converted.

  RETURN VALUES

    If an invalid character is encountered, both functions return (size_t)-
    1 and may set errno to indicate the error. Othewise, both functions return
    the number of the array elements modified (or required if pwcs is null),
    not including a terminating null code, if any. The array will not be null-
    terminated if the value returned is n.

  ERRORS

    Either function may fail if:

    [EILSEQ]
        Invalid byte sequence is detected.

  SEE ALSO

    mblen(3)

    mbtowc(3)

    wcstombs(3)

    wctomb(3)

  USAGE NOTES

    All of these functions are thread safe.

    None of these functions are async-signal safe.