1) but it does. If i can exchange a pointer to a struct and make use of it in both my application and the plugin dll (linked by a different compiler).
What would be an easier way, shipping a header + a (compiler dependant) .lib file?

2) I was just wondering whether the article exclusively referred to windows compiler regarding the compatibility, but apparently this is also true for linux and osx.

3) I think it's ok to have a x64 and a x86 version of a plugin.

Thanks for the reply!