Building as both a struct and a class?
Posted: Mon Apr 03, 2017 2:15 pm
I'm missing something, and I'm hoping for advice.
C++ normally complains if you don't use unique identifiers.
In Condition.h, we have
while in Building.h we have
Both of these headers are used in Building.cpp, and probably other places.
How is there not a conflict (since structs and classes are pretty much interchangeable)?
I was going to post an issue about renaming one of those Building variables (to reduce confusion), but I wanted to check if this was done by design (some overload trick I'm not thinking of).
C++ normally complains if you don't use unique identifiers.
In Condition.h, we have
Code: Select all
struct FO_COMMON_API Building : public ConditionBase {Code: Select all
class FO_COMMON_API Building : public UniverseObject {How is there not a conflict (since structs and classes are pretty much interchangeable)?
I was going to post an issue about renaming one of those Building variables (to reduce confusion), but I wanted to check if this was done by design (some overload trick I'm not thinking of).