Constant Being Initialized AFTER Variable That Uses It

I am having a problem with a constant I am defining in MSVC++ 6.0.

Basically, I declare a constant string exists in Test.h.

extern const std::string strTest;

In a cpp (other.cpp) file, I place the definition for strTest. It is marked as extern because without it, the constant would only be marked for internal linkage and results in a compiler error saying that strTest was never defined.

extern const std::string strTest = "Test";

In another cpp file (MyClass.cpp), I have a static member variable of a class. The declaration for the variable exists in MyClass.h. In MyClass.cpp I define the variable like so.

std::string MyClass::strPath = strTest;

However, when I run the code, strPath is filled with "" instead of "Test". I placed breakpoints on the strTest and strPath lines of code to see when each was occuring. I was suprised to find that the strPath line runs prior to the strTest line, and thus was initializing strPath with an uninitialized value of strTest. Is this expected behavior? I was under the impression that constants should be initialized before anything else.

Is there anyway to solve this problem to ensure that every constant defined in such a way is initialized before any attempt is made to use it? Thank you for any input you have.

Joe

You should place std::string strTest = "Test"; in global scope and extern std::string strTest; in your cpp. I am not sure if it can be a member of a class.
Why you want to do this?

strTest is defined in a global scope. strPath is the member of the class. strTest is a constant and strPath is a regular variable.

strTest is declared in Test.h, defined in other.cpp as shown in the lines of code above. strPath is declared as a static member variable in MyClass.h, and defined in MyClass.cpp as shown above.

Thanks for your input. I hope that clarifies the issue.

Place the extern declaration also in MyClass.h, before the class definition.

const variables are visible only to the file in which they are declared. That is why your class is not seeing it.

Quote:

---

Originally Posted by mercury529

strTest is defined in a global scope. strPath is the member of the class. strTest is a constant and strPath is a regular variable.

strTest is declared in Test.h, defined in other.cpp as shown in the lines of code above. strPath is declared as a static member variable in MyClass.h, and defined in MyClass.cpp as shown above.

---

Like this?

Code:

---

// MyClass.h
#ifndef MYCLASS_H
#define MYCLASS_H

#include <string>

class MyClass
{
public:
      static std::string strPath;
};

extern const std::string strTest;

#endif

---

Code:

---

// MyClass.cpp
#include "MyClass.h"

std::string MyClass::strPath = strTest;

---

Code:

---

// other.cpp
#include "MyClass.h"

const std::string strTest = "Test";

---

Code:

---

// main.cpp
#include <iostream>
#include "MyClass.h"

int main()
{
    MyClass object;
    std::cout << object.strPath << '\n';
    std::cin.get();
    return 0;
}

---

It would be like this

Code:

---

// MyClass.h
#ifndef MYCLASS_H
#define MYCLASS_H

#include <string>
#include "Test.h"

class MyClass
{
public:
      static std::string strPath;
};
#endif

---

Code:

---

// MyClass.cpp
#include "MyClass.h"

std::string MyClass::strPath = strTest;

---

Code:

---

// other.cpp

extern const std::string strTest = "Test";

---

Code:

---

//Test.h
extern const std::string strTest;

---

Code:

---

// main.cpp
#include <iostream>
#include "MyClass.h"

int main()
{
    MyClass object;
    std::cout << object.strPath << '\n';
    std::cin.get();
    return 0;
}

---

Edit: As you can tell from the example above Mario, I am including Test.h in MyClass.h, so strTest is known inside of MyClass.cpp where it is being assigned to strPath.

That has to be some problem with VC++ 6.0. Probably is is documented somewhere.

There is nothing wrong with your code. Main should output "test".

Compiler problem? const make the variable filescope, in other.cpp, it is const. So it is filescope. Don't make externs const.
[edit] extern keyword is not needed in other.cpp.

Const is no longer file scope when you define it as an extern const. If it were file scope, the linker would throw an error that it was undefined.

What is the alternative to making an extern const string? Defining the string in the header file results in multiple definitions. Prefacing it with static would work but also results in a lot more unnecessary variables floating in memory. Also, I favor any method that has the definition of the constants in the cpp file. I am trying to make it flexible in such a way that I can swap in .cpp files to work with different constants.

Thanks for any advice you can give.

Quote:

---

Originally Posted by siavoshkc

Compiler problem? const make the variable filescope, in other.cpp, it is const. So it is filescope. Don't make externs const.
[edit] extern keyword is not needed in other.cpp.

---

The extern keyword in other.cpp is not needed alright. When a variable is defined as it was in other.cpp, the extern keyword can be ommited. However it is considered good practice. It helps remember this particular const is to be used in other files...

And "don't make extern const"? You suggest the OP to not use a popular language feature?

Quote:

---

Originally Posted by mercury529

Const is no longer file scope when you define it as an extern const. If it were file scope, the linker would throw an error that it was undefined.

---

This is true. However you still have to declare the const in those files you wish to use it. Or the const will not be visible.

Quote:

---

Originally Posted by mercury529

What is the alternative to making an extern const string? Defining the string in the header file results in multiple definitions. Prefacing it with static would work but also results in a lot more unnecessary variables floating in memory. Also, I favor any method that has the definition of the constants in the cpp file. I am trying to make it flexible in such a way that I can swap in .cpp files to work with different constants.

---

Defining the const in a cpp file is what is bringing you problems in the first place. One possible way to override this behavior of VC++ 6.0 is perhaps define the const in the header file. Since this particular const of yours is initialized from a constant expression, it is itself a constant expression. You can, and probably should, define it in the header file.

It is, of course possible do what you are doing already. I just now tested your code to be absolute sure it works. And the obvious result is it does. But since VC++ 6.0 is not recognizing correctly the extern keyword, I can only suggest you move the definition to your header file. I'm sorry.

Quote:

---

The extern keyword in other.cpp is not needed alright. When a variable is defined as it was in other.cpp, the extern keyword can be ommited. However it is considered good practice. It helps remember this particular const is to be used in other files...

---

If you remove extern from the example code, you will get a linker error. Extern const in a cpp file is not a matter of good practice, as much as it is a necessity to be able to define a constant in a global way. The code simply does not work without it.

If I move the definition to the header file, how do I eliminate the re-defintion issue that occurs (when the header file is included in multiple files). Is making the const static the only way to get rid of it? I believed the better practice was to only mark the const as extern and then define in it in a cpp file. Unforunately, it appears that the MSVC++ 6 compiler runs into the assignment issue I originally detailed when I handle it this way.

Can anyone else reproduce this in MSVC++ 6.0? Does this code function correctly in Borland or G++? Could it have to do with an optimization setting? The issue I discovered was the const was getting assigned after the static variable. This just seems to go against what should occur.

Thanks again.

Quote:

---

Originally Posted by mercury529

Can anyone else reproduce this in MSVC++ 6.0? Does this code function correctly in Borland or G++? Could it have to do with an optimization setting? The issue I discovered was the const was getting assigned after the static variable. This just seems to go against what should occur.

---

With a little addition,

Code:

---

// other.cpp
#include <string>
extern const std::string strTest = "Test";

---

MSVC6: blank stare.
g++: expected result "Test".

Quote:

---

Originally Posted by mercury529

If you remove extern from the example code, you will get a linker error. Extern const in a cpp file is not a matter of good practice, as much as it is a necessity to be able to define a constant in a global way. The code simply does not work without it.

---

You are absolutely right about this. My bad. Too sleepy I guess.

Quote:

---

Originally Posted by mercury529

If I move the definition to the header file, how do I eliminate the re-defintion issue that occurs (when the header file is included in multiple files)

---

Well, you define it with internal linkage.

Code:

---

const std::string strTest = "Test";

---

And, you do provide header guards.

Quote:

---

Originally Posted by mercury529

Is making the const static the only way to get rid of it? I believed the better practice was to only mark the const as extern and then define in it in a cpp file.

---

It can be done so. As I said before, even with constants initialized from constant expressions. However C++ defaults const to have internal linkage. It feels natural to follow on this behavior. Also the compiler will be able to evaluate your const. With external linkage the compiler is left in the dark as to the actual value of the const.

Quote:

---

Originally Posted by mercury529

Unforunately, it appears that the MSVC++ 6 compiler runs into the assignment issue I originally detailed when I handle it this way.

---

I did some searching for you (as you probably did too by now), but came empty handed. Maybe my search string choices were not the best. But this is an old, unsuported and non standards conformant compiler. Do you really need to use it? ;)

Dave, I did have the <string> included.

Mario, yeah, you are right. I had multiple definitions lingering from incomplete removal from the other locations.

Are we agreed the behavior in MSVC++ 6 is incorrect for the code I wrote? I dislike having to put my definitions directly in the header file, but it looks as though I may have no choice. Unforunately I am stuck with MSVC++ 6 because it is the only legal version I own.

Thanks for all the input.

Joe

Quote:

---

Originally Posted by mercury529

Unforunately I am stuck with MSVC++ 6 because it is the only legal version I own.

---

Why not "buy" gcc?

Quote:

---

Originally Posted by Dave_Sinkula

Why not "buy" gcc?

---

Really, why not buy something if you plan on using it a lot?(sarcasm)

Quote:

---

Are we agreed the behavior in MSVC++ 6 is incorrect for the code I wrote?

---

Yes. It is definitely incorrect. Your code is fine.

Oh, I find the MSVC++ environment to be rather accomodating, especially when I am developing in Windows for windows with a lot of API programming. Also, it makes it easier when I have to deal with other developers who use MSVC++ as well.

I have only encountered a few other minor issues with MSVC++ even with reasonably heavy used of the STL. I do believe despite having some compiler issue, the MSVC++ 6 compiler was supposed to produce faster executables do to some compiler optimizations.

I don't think that to be true anymore. Not with 8 years on top of that to produce better and faster compilers. But I may be wrong.

I do agree that Visual Studio 6 was a great tool though. But I think if that is the only reason, you need to move on. VC++ 2005 Express Edition is free and, you will find, a much better product :)

I will test the code in my VC++6 and tell you if it works or not. But it may work if you don't make it const. Only in this case you can omit the extern keyword in other.cpp.

Yes, it worked correctly in my MSVC++6.
Please send complete code. For example you didn't include string in other.cpp.

Siav:
Thanks for the information. I do not want to make it non-const just to ensure I do not accidentally modify the string later down the line. The code, with the #include <string> added exhibits the error for me. I am using MSVC++ 6.0 SP6.

Mario:
If I am not mistaken, VC++ 2005 Express did not have the capability to create dll projects. I would happily move on, but for the moment, for the many aspects of my project, it is best to stay on MSVS 6 until I can afford a professional edition of .NET or 2005.

Call me Sia if you need a shorter name.
I use MSVC++6 without any service pack and it executed YOUR code correctly. So maybe there is some other problems with your code.