--- El lun 24-ene-11, Oliver Kowalke <k-oli@gmx.de> escribió:
De: Oliver Kowalke <k-oli@gmx.de> Asunto: [boost] [context] new version with stack-allocator Para: boost@lists.boost.org Fecha: lunes, 24 de enero de 2011, 10:00 boost vault contains a new version (0.4.0) where the user can provide its own stack allocator (the lib comes with a protected-stack allocator).
thanks for this change! i was precisely going to require passing a custom allocator to this (for a severely constrained system). just a question: Does the code relies on the 'standarese' assumption that allocators have to be stateless? the reason why i ask is because some of my code relies on allocators being stateful objects (yeah i know, break the standard and you are on your known, yadda yadda), hence it's ok if you do but i would like to know -Charles