Multiple definition of a function (MinGW)

[spirt]

Can anyone explain me why MinGW compiler gives multiple definition error about functions implemented in the two separate cpps and not declared in the headers?

[SixDegrees]

If the functions wind up in the same linkage, there's going to be a conflict. You must differentiate functions by name, argument list, namespace or some other scoping mechanism if they will be combined into a single executable or library.

[spirt]

I thought that cpp already provides a separate scope, if function declared and implemented only there and not exported, there shouldn't be any problem

[SixDegrees]

I thought that cpp already provides a separate scope, if function declared and implemented only there and not exported, there shouldn't be any problem

How could it possibly do that? If two definitions of the same function, with identical parameters, collide in the same linkage unit, there is no way for the linker to determine which one should be used. The preprocessor has nothing to do with this problem.

[squidge]

Can anyone explain me why MinGW compiler gives multiple definition error about functions implemented in the two separate cpps and not declared in the headers?

Well, you should be using a different class for the two seperate cpp files so this shouldn't be problem.

If you are using global functions then obviously defining the same function in two different cpp files will cause confusion at link time which to use, so either make one of them file local or put them in a class. Same goes for global variables. The linker is not going to check to see if you have included such functions in a header file.

[Santosh Reddy]

Can anyone explain me why MinGW compiler gives multiple definition error about functions implemented in the two separate cpps and not declared in the headers?

Even though functions are implemented in two separate source files, if they belong to same namespace, the linker would be confused which one to use for linking and ends up in throwing error.

I thought that cpp already provides a separate scope, if function declared and implemented only there and not exported, there shouldn't be any problem

Yes both the functions have different scope (as not declared in include files), but scopes are different for compiler & linker. For compiler, scope is single translated unit (including any extern symbols). Linker's job is to connect all the translation units, to so form the final executable, so for linker the scope includes all translations units, and hence the error.

C++ provides various ways to deal with situation, like namespace separation, object encapsulation using classes / structs, function overloading etc, you can use one of these methods.

[FelixB]

I'd suggest to use anonymous namespaces to avoid such conflicts:

//a.cpp
namespace
{
  void function() {...}
}
 
//b.cpp
namespace
{
  void function() {...}
}

//a.cpp
namespace
{
  void function() {...}
}

//b.cpp
namespace
{
  void function() {...}
}

To copy to clipboard, switch view to plain text mode