Back to General and Gameplay Programming

Two classes, same name - solution?

Julian Watzinger · 2013-05-04T14:31:55

Hello, after refactoring some of my old gui code by removing the "Gui" - prefixes and instead putting them into a gui-namespace, plus putting the file into a seperate folder, I've come across a problem. Now I've got some classes that share the same name, and also the same file-name: // in "Gui/Window.h" namespace gui { class Window {}; } // in "Core/Window.h" namespace core { class Window {}; } Those two classes doesn't have anything in common. Before starting, I supposed this was safe, since both files are in different locations, and both classes are in different namespaces. However, when compiling the libary I get a compiler warning about multiple object-files with the same name, and upon compiling the actual game project, I get a lot of unresolved symbol linker errors. Now I ask, is there any way to solve this, without adding some provisorical pre/postfix to the class?

General and Gameplay Programming Programming

Started by Juliean May 02, 2013 09:59 PM

19 comments, last by Juliean 10 years, 11 months ago

Juliean

7,344

Author

May 04, 2013 02:31 PM

The solution is to either change the filename or change the target filename (or wait until Microsoft fixes this bug, but it's been around for ages so I'm not counting on them fixing it any time soon).

Well, I kinda see why they aren't putting much effort into fixing this, since the easiest and probably best solution actually consits of only changing one option, namely the "output object file as"-option for the whole project to:


%(RelativeDir)\$(IntDir)

That way every object file gets put where it should automatically. Would be nice still as a default. Or is there any drawback by that?

Two classes, same name - solution?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Two classes, same name - solution?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines