User Tools

Site Tools


2014:polymorphic_allocators_for_fundamental_libraries

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
2014:polymorphic_allocators_for_fundamental_libraries [2013/12/09 15:33] jonjagger2014:polymorphic_allocators_for_fundamental_libraries [2016/06/11 14:05] (current) – external edit 127.0.0.1
Line 6: Line 6:
 **Duration**: 90 mins\\ **Duration**: 90 mins\\
 **Description**: \\ **Description**: \\
-One of the key resources in any C++ program is memory, as every object must, if nothing else, occupy some memory itself.  Unsurprisingly, this has lead to many attempt to find 'a better memory allocator', often with competing priorities.  Do you want a faster allocator? Thread-specific allocation? Or more "secure"?  Do you want to better track leaks and report+One of the key resources in any C++ program is memory, as every object must, if nothing else, occupy some memory itself.  Unsurprisingly, this has lead to many attempt to find "a better memory allocator", often with competing priorities.  Do you want a faster allocator? Thread-specific allocation? Or more "secure"?  Do you want to better track leaks and report
 errors?  Or simply monitor usage patterns?\\ errors?  Or simply monitor usage patterns?\\
 \\ \\
2014/polymorphic_allocators_for_fundamental_libraries.1386603234.txt.gz · Last modified: 2016/06/11 14:05 (external edit)