object multi reference

[Gary Wessle]

Hi

I have a program consisting of few .cpp and .h files with few
classes. the objects need to read and write to the disk and check on
what other objects are doing. to centralize the disk-location info, I
created a g_inf class which serves as placeholder of paths for
directories and files info.

class g_inf{
string building_dir;
string tenants_dir;
string tena_file_ext;
...
public:
g_inf();
};
g_inf::g_inf()
: building_dir("/path/"),
...
{}

in the main, I do

int main(){
g_inf dsk_inf();
myType group(&dsk_inf, ...
anotherType them(&des_inf, ...
thirdType(&dsk_inf, &myType, ...

is this a safe way to do it?

thanks

[Alan Johnson]

Gary Wessle wrote:

Hi

I have a program consisting of few .cpp and .h files with few
classes. the objects need to read and write to the disk and check on
what other objects are doing. to centralize the disk-location info, I
created a g_inf class which serves as placeholder of paths for
directories and files info.

class g_inf{
string building_dir;
string tenants_dir;
string tena_file_ext;
...
public:
g_inf();
};
g_inf::g_inf()
: building_dir("/path/"),
...
{}

in the main, I do

int main(){
g_inf dsk_inf();

This declares a function named dsk_inf that takes 0 parameters and
returns a g_inf. Very likely not what you intended to do. Try:

g_inf dsk_inf;

myType group(&dsk_inf, ...
anotherType them(&des_inf, ...
thirdType(&dsk_inf, &myType, ...

is this a safe way to do it?

thanks

This seems like a safe way, yes, though if it is just a bunch of global
data you may want to consider just using a namespace. i.e:

// g_inf.h

namespace g_inf
{
extern const string building_dir ;
// other data
}
// g_inf.cpp

namespace g_inf
{
const string building_dir("/path/") ;
// other data
}
If it is more than just data then the Singleton or Monostate patterns
may apply (though in my opinion these patterns should be used sparingly
and only after several other designs have been considered).

--
Alan Johnson