3 ms·
OpenBSD man page (https://man.openbsd.org/isalnum.3 https://man.openbsd.org/isalnum.3): “OpenBSD always uses the C locale for these functions, ignoring the glo
by Someone 5y ago
OpenBSD man page (https://man.openbsd.org/isalnum.3 https://man.openbsd.org/isalnum.3):
“OpenBSD always uses the C locale for these functions, ignoring the global locale, the thread-specific locale, and the locale argument.“
and https://man.openbsd.org/setlocale.3 https://man.openbsd.org/setlocale.3:
“On OpenBSD, the only useful value for the category is LC_CTYPE. It sets the locale used for character encoding, character classification, and case conversion. For compatibility with natural language support in packages(7), all other categories — LC_COLLATE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, and LC_TIME — can be set and retrieved, too, but their values are ignored by the OpenBSD C library. A category of LC_ALL sets the entire locale generically, which is strongly discouraged for security reasons in portable programs.”
Probably non-standard, but from what I read here, also a defensible choice.
- matheusmoreira 5y agoThat's interesting! Non-standard but it doesn't matter. That's the right thing to do no matter what some piece of paper says.