On Sun, 19 Jun 2011 12:29:41 -0500 Bryce Lelbach <blelbach@cct.lsu.edu> wrote:
The proposed Boost.Xint does not fulfill the thread-safety promises that it makes. The library uses a custom allocator (allocator_t), which uses global variables and does not protect them with a synchronization primitive. [...]
What global variables are those? The only non-local variables I see from a quick perusal of allocator_t are fixed_length and magnitude_datasize (allocator_t static consts) and minimum_digits (a global const).
Can the author of this library please make the custom allocation strategy optional? [...] I think the better solution here is to not tie Boost.Xint to a particular memory allocation scheme.
If I work on it any further (still undecided), that's already on the to-do list. -- Chad Nelson Oak Circle Software, Inc. * * *