Submitter:Fred J. Tydeman
Document: WG14 N1944
220.127.116.11 strcoll makes the assumption that the result of comparing two strings can only have one of three outcomes: greater than, equal to, or less than. However, there is a fourth outcome that is possible: not comparable.
I have been told that there are locales or codesets that have strings of bytes that do not form valid characters. Those invalid characters could be considered Not-a-Character (similar to Not-a-Number for floating-point). And, they are not comparable to anything.
I do not know if the same issue can apply to wchar_t. If so, then 18.104.22.168.1 wcscmp(), 22.214.171.124.3 wcsncmp(), and 126.96.36.199.5 wmemcmp() have the same problem.
Suggested Technical Corrigendum
Replace the start of 188.8.131.52, paragraph 3,
The strcoll ...
If either string contains invalid characters, errno is set to an implementation defined value and the return value is unspecified; otherwise, errno is left alone and the strcoll ...
The same change should also be applied to 184.108.40.206.2 wcscoll.