Re: Passing Pointers -- where to delete them
On Mar 3, 5:09 pm, "jason.cipri...@gmail.com"
<jason.cipri...@gmail.com> wrote:
On Mar 3, 5:48 am, James Kanze <james.ka...@gmail.com> wrote:
[...]
[concerning singletons...]
Like most things, they can be overused, but a few special cases
do occur to me. I use at least two regularly: one for "program
state" (which will define the return value of main in the end),
and one for the command line---the "options" are static
variables which enrol with it, and are automatically processed
when the singleton object is passed argc and argv. My
configuration file data is usually a singleton as well, as is
the log manager.
I sometimes use it for command line options if I need to put
something together quickly (even then I try to keep the
command line data local to main and pass around the relevant
parts as needed),
Actually, I've found it preferable for individual components to
handle their own options, with no global specification of the
complete list of options anywhere. At least in a lot of cases.
although I've found a lot of merit in merging command line
options and configuration file data into the same set of
configuration data.
For programs which have configuration files, it's often
desirable to allow specific configuration data to be overridden
by command line options, I agree, and my configuration
management software supports this. That doesn't mean that there
won't be options which can't appear in the configuration file.
(The name of the configuration file, for example, is almost
always a command line option.)
For configuration data, I generally keep everything as static
members of a class -- which does have the same end effect sans
the GetInstance(), so I suppose it's not much different; same
with logging.
Yes. I was using "singleton" in a more generic sense: in my
case, for example, each option is actually a static variable (at
namespace scope); CommandLine is a true singleton, however,
since it is accessed by the constructors of the options.