4 ms·
I understood K&R years ago, but somehow I feel completely inadequate to being a C programmer. I think there is some kind of black art involved in memory managem
by Tichy 16y ago
I understood K&R years ago, but somehow I feel completely inadequate to being a C programmer. I think there is some kind of black art involved in memory management. I checked recently and it seems K&R doesn't even talk much about memory management.
I just wish to learn the current state of the art - what are best practices that have evolved since K&R?
- alnayyir 16y agoThat feeling of inadequacy and incompleteness post-K&R is something I experienced too and is something I'm hoping to address.
- silentbicycle 16y agoThere's a chapter on memory management* in Hanson's _C Interfaces and Implementations_ (http://sites.google.com/site/cinterfacesimplementations/ http://sites.google.com/site/cinterfacesimplementations/), which is one of the better advanced C books I've read. * Mostly, arena-based allocators. Paul Wilson's "Uniprocessor Garbage Collection Techniques" (http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.47.2438 http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.47.2...) is an excellent overview, as is Jones and Lins's _Garbage Collection: Algorithms for Automatic Dynamic Memory Management_.
- mahmud 16y agoInterested parties can also look into "Memory as a Programming Concept in C and C++".