In the following code:
It seems that the constructor is being called between the time I create the parser and the time that it is used one line below. Any ideas why this might be the case?Code:iniFileParser parser = iniFileParser(fname); if(!parser.getValue("State", "width", &width)) { ... }
Assuming that you are talking about an iniFileParser constructor, it would be because this constructs an iniFileParser object named parser:
If you are talking about the iniFileParser destructor, then it would be because you create a temporary and copy from it (after which the copy is destroyed), and the compiler did not optimise away the extra copy in this case, perhaps because optimisations were not enabled. You should just write:Code:iniFileParser parser = iniFileParser(fname);
Code:iniFileParser parser(fname);
Look up a C++ Reference and learn How To Ask Questions The Smart WayOriginally Posted by Bjarne Stroustrup (2000-10-14)
Thanks...that makes sense!
If you are doing something with side effects in the destructor (eg, print a message), the compiler can't optimize it out, otherwise it will be changing the behaviour of your program.
Yes it can. The C++ standard explicitly allows the compiler to eliminate any object if the only way of detecting the existence of that object is by tracking calls of constructors and destructors. This specifically allows the compiler to avoid constructing or destructing objects unnecessarily. A side effect of that is that any side-effects of constructors and destructors are not guaranteed to occur.
Ah never knew that.
Stand corrected.
