linkage

For me it's a rule to define and declare static functions inside source files, I mean .c files. However in very rare situations I saw people declaring it in the header file. Since static functions have internal linkage we need to define it in every file we include the header file where the function is declared. This looks pretty odd and far from what we usually want when declaring something as static. On the other hand if someone naive tries to use that function without defining it the compiler will complaint. So in some sense is not really unsafe to do this even sounding strange. My questions

How can I remove this link warning? You can see code segment that causes this warning. static AFX_EXTENSION_MODULE GuiCtrlsDLL = { NULL, NULL }; //bla bla // Exported DLL initialization is run in context of running application extern "C" void WINAPI InitGuiCtrlsDLL() { // create a new CDynLinkLibrary for this app new CDynLinkLibrary(GuiCtrlsDLL); // nothing more to do } warning C4273: 'InitGuiCtrlsDLL' : inconsisten t dll linkage I have also export and import definitions, like: #ifdef _GUICTRLS #define GUI_CTRLS_EXPORT __declspec(dllexport) #else #define GUI_CTRLS_EXPORT __declspec(dllimport)

How can one register a dependency property whose value is calculated using the value of another dependency property? Because the .NET property wrappers are bypassed by WPF at run-time, one should not include logic in the getters and setters. The solution to that is typically to use PropertyChangedCallback s. But those are declared static. For example, what is the proper way to accomplish this contrived task: public bool TestBool { get { return (bool)GetValue(TestBoolProperty); } set { SetValue(TestBoolProperty, value); TestDouble = ((value)?(100.0):(200.0)); // HERE IS THE DEPENDENCY } }

According to (c) ANSI ISO/IEC 14882:2003, page 127: Linkage specifications nest. When linkage specifications nest, the innermost one determines the language. A linkage specification does not establish a scope. A linkage-specification shall occur only in namespace scope (3.3). In a linkage-specification, the specified language linkage applies to the function types of all function declarators, function names, and variable names introduced by the declaration(s). extern "C" void f1(void(*pf)(int)); // the name f1 and its function type have C language // linkage; pf is a pointer to a C function

I know that scipy.cluster.hierarchy focused on dealing with the distance matrix. But now I have a similarity matrix... After I plot it by using Dendrogram, something weird just happens. Here is the code: similarityMatrix = np.array(([1,0.75,0.75,0,0,0,0], [0.75,1,1,0.25,0,0,0], [0.75,1,1,0.25,0,0,0], [0,0.25,0.25,1,0.25,0.25,0], [0,0,0,0.25,1,1,0.75], [0,0,0,0.25,1,1,0.75], [0,0,0,0,0.75,0.75,1])) here is the linkage method Z_sim = sch.linkage(similarityMatrix) plt.figure(1) plt.title('similarity') sch.dendrogram( Z_sim, labels=['1','2','3','4','5','6','7'] ) plt.show() But here is the outcome