Databases
StackOverflow2013
Postsdbo
PODll compatibility between compilers
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODll compatibility between compilers
    primarykey
    data
    text
    <p>Is there some way to make c++ dlls built with diffrent compilers compatible with each other? The classes can have factory methods for creation and destruction, so each compiler can use its own new/delete (since diffrent runtimes have there own heaps).</p> <p>I tried the following code but it crashed on the first member method:</p> <p>interface.h</p> <pre><code>#pragma once class IRefCounted { public: virtual ~IRefCounted(){} virtual void AddRef()=0; virtual void Release()=0; }; class IClass : public IRefCounted { public: virtual ~IClass(){} virtual void PrintSomething()=0; }; </code></pre> <p>test.cpp compiled with VC9, test.exe</p> <pre><code>#include "interface.h" #include &lt;iostream&gt; #include &lt;windows.h&gt; int main() { HMODULE dll; IClass* (*method)(void); IClass *dllclass; std::cout &lt;&lt; "Loading a.dll\n"; dll = LoadLibraryW(L"a.dll"); method = (IClass* (*)(void))GetProcAddress(dll, "CreateClass"); dllclass = method();//works dllclass-&gt;PrintSomething();//crash: Access violation writing location 0x00000004 dllclass-&gt;Release(); FreeLibrary(dll); std::cout &lt;&lt; "Done, press enter to exit." &lt;&lt; std::endl; std::cin.get(); return 0; } </code></pre> <p>a.cpp compiled with g++ g++.exe -shared c.cpp -o c.dll</p> <pre><code>#include "interface.h" #include &lt;iostream&gt; class A : public IClass { unsigned refCnt; public: A():refCnt(1){} virtual ~A() { if(refCnt)throw "Object deleted while refCnt non-zero!"; std::cout &lt;&lt; "Bye from A.\n"; } virtual void AddRef() { ++refCnt; } virtual void Release() { if(!--refCnt) delete this; } virtual void PrintSomething() { std::cout &lt;&lt; "Hello World from A!" &lt;&lt; std::endl; } }; extern "C" __declspec(dllexport) IClass* CreateClass() { return new A(); } </code></pre> <p>EDIT: I added the following line to the GCC CreateClass method, the text was correctly printed to the console, so its defenatly the function call thats killing it. </p> <pre><code>std::cout &lt;&lt; "C.DLL Create Class" &lt;&lt; std::endl; </code></pre> <p>I was wondering, how does COM manage to maintain binary compatibility even across languages, since its basicly all classes with inheritence (although only single) and therefore virtual functions. I'm not massivly bothered if I cant have overloaded operators/functions as long as I can maintain the basic OOP stuff (ie classes and single inheritence).</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdandan78
    1. USFire Lancer
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODll compatibility between compilers
      1. USReunanen
      1. VTFavorite
    2. VO
      singulars
      1. PODll compatibility between compilers
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODll compatibility between compilers
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow does COM do it? With lightweight RPC calls - you could build your app using dce-rpc and you'd get the same results. In no case does COM provide a pointer to an external dll's memory, it makes function calls to that dll.
      singulars
      1. PODll compatibility between compilers
      1. USgbjbaanb
    2. COThe following articles [here](http://eli.thegreenplace.net/2011/09/16/exporting-c-classes-from-a-dll/), [here](http://www.codeproject.com/Articles/28969/HowTo-Export-C-classes-from-a-DLL#CppMatureApproach), and [here](http://chadaustin.me/cppinterface.html) may be helpful. Your code example is almost there except for the inlined virtual destructor. AFAIK, all methods in your abstract interface must be pure virtual `=0`.
      singulars
      1. PODll compatibility between compilers
      1. USgreatwolf
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload