3 ms·
I too am surprised. The author generally writes clean code, most of it seems to rely heavily on libC… I am confused…
by jdefr89 4y ago
I too am surprised. The author generally writes clean code, most of it seems to rely heavily on libC… I am confused…
- eqvinox 4y agoThe article is indeed rather fuzzy about what "libc" is. It seems to exclude "things provided by the compiler" while talking about varargs, but later calls out atomics with no such note.
- arka2147483647 4y agoThe subject is messy. For example; traditionally memset() and memcpy() are clib functions, but ofcourse nowdays any good compiler will intrisic or optimize those. Same for atomics.
- deleted 4y ago[deleted]
- spc476 4y agoIf you follow the links, most of the complaints stem from the Microsoft Windows implementation of the C Standard.