Ivan Vecerina wrote:
"Thorsten Ottosen" <thorsten.ottosen@dezide.com> wrote in message news:444CB0DC.3040501@dezide.com...
: > Is the performance of those libraries measurably hit? : : Yes (I havn't looked at how std::vector is used in ASIO, but I can't see : how it could get around the problem). : : > If so, maybe you want a pod_vector, which will also benefit : > from relying on realloc. No big deal. : : It's not just for PODs.
How would you fill a non-POD vector with uninitialized data ?
If subsequent in-place construction fails, the memory needs to be removed again without calling constructors.
: It remains to be seen how many user wishes that can be crammed : into the interface in a reasonable manner.
It is exactly my point: I doubt that a sufficiently complete and consensual value & object conversion interface can be completed on time. So my suggestion is to go ahead with what we have or can do now, but make it a non-member interface to allow future evolution.
I fail to see how really disallow future evolution to have members. -Thorsten