Re: initializing static members of class

From:

archimed7592 <archimed7592@gmail.com>

Newsgroups:

comp.lang.c++

Date:

28 May 2007 12:17:24 -0700

Message-ID:

<1180379844.561792.284940@u30g2000hsc.googlegroups.com>

On May 28, 9:29 pm, prakash.mi...@gmail.com wrote:

On May 28, 7:30 pm, Erik Wikstr=F6m <eri...@student.chalmers.se> wrote:

On 28 Maj, 16:25, "John" <prakash.mi...@gmail.com> wrote:

Hello,

is there any compiler option for g++ for initializing static members =

of the

class.
Due to some unknown reason, static member in one of our c++ applicat=

ion is

not getting initialized properly.

Most probable reason for this is that you do not initialize it in the
code, but you have not shown us any code so we can't tell.

--
Erik Wikstr=F6m

FYI

Here is the code:

Application is using below mentioned template class which is declared
as static in RuleEngine.h class file.

static RWTPtrHashDictionary<RWCString, RuleClass
RWDefHArgs(RWCString)>ruleHash;

RWTPtrHashDictionary<RWCString, RuleClass RWDefHArgs(RWCString)>
  RuleEngine::ruleHash(RWCString::hash);

Above line definition/initialization for ruleHash is found in
RuleEngine.C at the beginning of the file.

Here is sample piece of code where ruleHash is used. This code is
RuleEngine.C. I am calling insertRule(this) static method from
RuleClass.h class file.

Void RuleEngine::insertRule( RuleClass* newRule )
{
   RuleClass* rule = NULL;
   if( 0 != ruleHash.entries() )
    ............
   Core dump....

}

Application is using template object ruleHash to call entries()
method.
I am getting core dump at releHash.entries() line. Its not only with
entries method, it crashes for any methods of RWTPtrHashDictionary.
I have also tried with other template class RWTValDlist<RWCString> to
test whether it is problem with deprecated RWTPtrHashDictionary
template.
But I see that application crashes for RWTValDlist template too.

Please help me.

Thanks,
Prakash

It seems RWCString::hash is constructed after the
RuleEngine::ruleHash(and result is unpredictable)...
Use Singleton pattern to fix that.