jonathrg

14 ms·

1. 181.▲
   by jonathrg 5y ago

   It's too bad that many of the string handling functions in the C standard library are ticking time bombs. I like the approach taken in e.g. git which converts problematic function calls into compile errors https://github.com
2. 182.▲
   by jonathrg 5y ago

   That's MINIX.
3. 183.▲
   by jonathrg 5y ago

   That seems like about the right proportion to me - struct solves a much more common problem than restrict does. And to be fair, it is a lesser known feature. But user-the-name is implying that restrict is somehow difficult to use or underst
4. 184.▲
   by jonathrg 5y ago

   What? I use it whenever I have a function that takes two or more pointers if I know they can't refer to overlapping memory. And it's part of the signature for memcpy since C99
5. 185.▲
   by jonathrg 5y ago

   Doesn't the restrict keyword solve this?
6. 186.▲
   by jonathrg 5y ago

   That's surprising. I understand the desire to keep Multics alive for the sake of preserving history, but why would you want to release new features for it?
7. 187.▲
   by jonathrg 5y ago

   Their conclusion, "security issues are common in PyPI packages", doesn't really follow from the results. Their methods will classify any use of a function that is not cryptographically secure (MD5, random), even if it is no