Dynamic Library: Do you need to export variables of a class?

Quote:

---

Originally Posted by 2kaud

and why the dll interfaces need to be 'C' and not C++!

---

Well if I'm compiling the project myself, I won't probably have any problems but if others need to compile it in other operating systems too , from what i read from your links i will have a problem. If i program every dll in C i won't have problems with the compilers right?

If the .exe(s) and the .dll(s) are compiled with exactly the same version of the compiler/stl etc then there shouldn't be a problem. If an .exe or another .dll is compiled with say version w.x.y and this .dll is compiled with version w.x.z then yes, you could well have a problem. If you are distributing .dll(s) as upgrades to big projects you need to have the .dll(s) interfaces as 'C' so that it doesn't matter if the version of the compiler/stl that was used to compile the .dll is not the same as that used to compile the .exe(s).

Now I know everything I need to know! You really helped me all of you. I never expected that dlls would have to much you need to know. A last question. Does the same things are applied to linux shared libraries? Should I search more about it?

Sorry - I can't help you with Linux as I only use Windows/MSVS.