DaveFlater

SI avoids identifying countable entities and events except in special cases like bequerel. This is but one example among many where the needs of IT are outside the scope that SI serves. https://www.researchgate.net/publication/339954122_Quantitie...

There they go with Dickens again. Why always Dickens? Haven't we suffered enough?

See: https://news.ycombinator.com/item?id=36393673

GCC optimization causes the frame pointer push to move around, resulting in wrong call stacks. "Wontfix"

https://news.ycombinator.com/item?id=38896343

Whether over months or years, they have certainly gotten worse. It is a race to the bottom or to 1 micrometer above the legal red line if one should ever be established.

CFPB and FTC talked about it: https://www.consumerfinance.gov/compliance/circulars/consume...

Summary of comparable talk in the EU: https://www.insideprivacy.com/eu-data-protection/the-eu-stan...

Down in the details, it looks like there has been enforcement in individual cases, but it obviously was not enough to stop the flood.

In C++ this is simply legal code. But in C, the bogus warning has now escalated to a bogus error.

   void fun110 (char const * const *a) {}
   char **a;
   fun110(a);

What makes it seem probable that it is patent-encumbered? Is there something specific I can read about or is it just the track record of previous standards (starting with arithmetic encoding in the first JPEG)?