20 Mar
2008
20 Mar
'08
8:19 p.m.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 20 March 2008 15:59 pm, Mathias Gaunard wrote:
The first part of what I propose is a policy-based self-containing non-typed memory allocator framework that would allow pluggable usage of SBO, and that could provide the never-empty guarantee with one technique or the other if desired.
What does SBO stand for? - -- Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH4sbR5vihyNWuA4URAvFYAKC0ufpRjQXHo2BckygL4xPAG8bUbgCePoa2 LAHDlwxTvam9HsfEGaNTsmI= =Ndmf -----END PGP SIGNATURE-----