ybungalobill

4 ms·

1. 1.▲
   by ybungalobill 10y ago

   The standard does not specify what the standard exceptions return from what(). It does not have to be in English. Why care about it's prototype? You may want to embed into what() unicode strings that describe the error and came from el
2. 2.▲
   by ybungalobill 14y ago

   I agree in principle. But "chatty" APIs usually work with short strings, in which case you can use stack allocations in those performance critical calls.
3. 3.▲
   by ybungalobill 14y ago

   I believe the authors wrote it clear enough that they don't rule out UTF-16 completely: > We believe that all other encodings of Unicode (or text, in general) belong to rare edge-cases of optimization and should be avoided by mainstream
4. 4.▲
   by ybungalobill 14y ago

   Man, the article doesn't try to argue for or against UTF-8 based on lexicographical order. It's in the "facts" section, and it's a correct fact. So it's just as neutral as "Widechar is 2 bytes [...] 4 on others." or "In both [...] character
5. 5.▲
   by ybungalobill 14y ago

   AFAIK the correct term is "byte oriented".