On Windows, I plan to create a ptr_vector in a separate DLL and propagate it to the executable for ownership (Factory-style). The executable will be responsible for the lifetime of this ptr_vector, and will eventually result in &quot;delete&quot; being called on each element in the ptr_vector. However, this &#39;delete&#39; will be from the executable&#39;s memory manager, when the memory was originally allocated in the shared library&#39;s memory manager, causing serious issues.<div>
<br></div><div>It would be ideal to specify a delete_clone class that ptr_vector would use (via ADL) and would force those objects in the ptr_vector to use the &#39;delete&#39; call from the DLL&#39;s memory manager, and not the executable&#39;s.</div>
<div><br></div><div>I don&#39;t see that this is going to be possible, or at least able to be done easily. Since the delete_clone&#39;s operator will have to be implemented in a CPP file, so it will be included into the shared library. This also implies that I&#39;ll have to import the delete_clone&#39;s interface, since this DLL will be loaded dynamically with LoadLibrary() in Windows. I just don&#39;t see this happening.</div>
<div><br></div><div>Now, if ptr_vector had a function like so:</div><div><br></div><div>ptr_vector::set_deleter()</div><div><br></div><div>I could give it a pointer to a global function in my DLL, and the deleter becomes fully transparent to my executable. It just has to keep the ptr_vector around and let it fall out of scope and the deleter from the DLL will be used to delete each object in the ptr_vector. However, it isn&#39;t this simple and I need advice on how I can make this work.</div>
<div><br></div><div>Thanks.</div>