Home
last modified time | relevance | path

Searched hist:"9981 ef2702b1f3f392f1059ce4c97314db3afdff" (Results 1 – 2 of 2) sorted by relevance

/freebsd/lib/libc/locale/
H A Dtolower.3diff 9981ef2702b1f3f392f1059ce4c97314db3afdff Thu Oct 03 13:14:00 CEST 2002 Tim J. Robbins <tjr@FreeBSD.org> Point out that although toupper() and tolower() really accept rune_t's
and not just unsigned char's, callers should use towupper() and towlower()
instead when working with wide characters if portability is a concern.
diff 9981ef2702b1f3f392f1059ce4c97314db3afdff Thu Oct 03 13:14:00 CEST 2002 Tim J. Robbins <tjr@FreeBSD.org> Point out that although toupper() and tolower() really accept rune_t's
and not just unsigned char's, callers should use towupper() and towlower()
instead when working with wide characters if portability is a concern.
H A Dtoupper.3diff 9981ef2702b1f3f392f1059ce4c97314db3afdff Thu Oct 03 13:14:00 CEST 2002 Tim J. Robbins <tjr@FreeBSD.org> Point out that although toupper() and tolower() really accept rune_t's
and not just unsigned char's, callers should use towupper() and towlower()
instead when working with wide characters if portability is a concern.
diff 9981ef2702b1f3f392f1059ce4c97314db3afdff Thu Oct 03 13:14:00 CEST 2002 Tim J. Robbins <tjr@FreeBSD.org> Point out that although toupper() and tolower() really accept rune_t's
and not just unsigned char's, callers should use towupper() and towlower()
instead when working with wide characters if portability is a concern.