<div><div dir="auto">Haven’t used msvc in a while, but if I remember correctly, each dll has it’s own heap, so you can’t allocate in one and delete in another — unless you buy the professional version.</div><div dir="auto"><br></div><div dir="auto">Not sure if this applies, but hope it helps...</div><div dir="auto">don </div><br><div class="gmail_quote"><div>On Thu, Nov 9, 2017 at 9:47 PM barbara via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
We have a contributor who is working on porting CopperSpice to compile<br>
with MSVC 2017 and/or the clang Windows ABI compatible tool chain. There<br>
seems to be a potential problem and we are not sure if this is serious.<br>
Options: some wonderful person points us to a workaround, there is a<br>
decent solution using the clang front end, jump up and down and hope MS<br>
will correct this.<br>
<br>
In our library we have a templated class with a data member whose type<br>
is std::deque<T>. This class is in "lib_a.dll" and is used in<br>
"lib_b.dll" and the main executable.<br>
<br>
We have read/been told the following: "The only STL container that can<br>
currently be exported is std::vector. The other containers ( map, set,<br>
queue, list, deque) all contain nested classes and can not be exported."<br>
So according to MSDN docs it is impossible to export the STL<br>
containers, like deque. Does this limitation exist in clang when using<br>
the MSVC compatible ABI on Windows?<br>
<br>
Something does not add up here and I will admit I am not sure I fully<br>
understand the problem. Our hope is that someone can see through this<br>
issue and help us define the real problem and offer a suggestion.<br>
<br>
Any ideas or a potential direction is appreciated.<br>
<br>
<br>
Barbara<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antivirus</a><br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div></div>