59d41e37   
   From: moreno_news@mailinator.com   
      
   > Any suggestions on other ways of doing this or if there is a simple   
   > fix to this problem?   
      
   I think if you make NAME a static member function   
   you would avoid the problem  (*if* the problem is   
   indeed caused by order of initializations of static   
   data members):   
      
   > // Generic definition of template   
   > template   
   > struct TypeNameTraits   
   > {   
   >         static const std::string NAME;   
   > };   
   > template  const std::string   
   > TypeNameTraits::NAME = "!UNKNOWN_TYPE_NAME!";   
      
   template    
   struct TypeNameTraits   
   {   
       static string name()   
       {   
           return "unknown_type_name";   
       }   
   };   
      
   template<>   
   struct TypeNameTraits   
   {   
       static string name()   
       {   
           return "int";   
       }   
   };   
      
   // etc.   
      
      
   HTH,   
      
   Carlos   
   --   
      
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)