Required to link windows header modules (?)

[Sean Kelly]

The standard C headers I've defined don't need to be linked against my 
app in any circumstances I've encountered so far--they serve as pure 
import modules.  However, I've recently discovered that this does not 
hold true for the Windows headers I use, which seem to require me to 
link against them if I reference any struct they declare.  Is it 
possible that extern (C) declarations tell the compiler that the struct 
will be available elsewhere and extern (Windows) doesn't?  It's worth 
noting that the link errors I get display a D-style mangled name for the 
struct definitions rather than a C-style name as I'd expect.  Should 
these structs all be declared as extern (C)?


Sean