News for hackers. Stuff that matters.
Re:The Horror in the Standard Library by spc476 on Saturday May 06, 2017 @01:15AM (#14278801)
Or a call to strlen() which makes your 120 cycles of latency start to look good ...

Edit to add: I've used both malloc()/free() and a custom memory allocation API that required the size to be passed in. I found the second API to be much more of a pain to use over the long term. Besides, it wastes memory because the memory API will have to track the size anyway to detect misuse of the API (or else blindly trust that the right size is passed in and hilarity ensues when it's not ...).

Re:The Horror in the Standard Library by makapuf on Saturday May 06, 2017 @04:11AM (#14279263)
Well you could use free() whenever it's practical and free_sz () when you can get the performance.