Thread: extern "C"

Yes, in strange places, you may need to "do more" to make it work - it's pretty obvious when you do, so unless you are compiling HUGE chunks of code, it should (now that you are aware of it) be possible to rectify pretty easily.

Of course, it's also a good idea to make typedefs of your function pointer types anyways - because it makes the function pointer easier to use generally, so the second pattern in the linked article is probably a good idea.

--
Mats

If you feel it unsafe, you can always add extern "C" to your definitions as well. Then there will be no problems such as mentioned in the article.

Originally Posted by George2

1. We should add extern to declaration, so what we know we are referring a function/variale from other compile unit;

Yes and no. Functions are already visible in all compilation units, so no extern is required at all.
For variables, you do indeed need to add a declaration with extern before it.

2. We should also add extern to definition so that this function/variale is visible to other compile unit. In this case, extern is on the other side of static.

No. All variables and functions have external linkage by default. That means you can access them from other compilation units by default. You can override this by adding "static" before them. In that case, you can't use the functions/variables in other compilation units.

I'm only 90% sure about the functions side of the argument, but the variables should be right.