From: 0xCDCDCDCD@gmx.at   
      
   On 22.04.2012 13:20, Dave Harris wrote:   
   > roberts.noah@gmail.com (nroberts) wrote (abridged):   
   >> Say you were given a coding policy that stated, "Only initialize   
   >> members with non-trivial constructors and destructors in your   
   >> constructor's initialization list."  (...)   
   >   
   > They may be trying to say that:   
   > (...)   
   >   
   > Basically, assignment statements are simple. Everyone understands   
   > them.  Initialisation lists are weird and full of restrictions and   
   > special cases; they are part of what makes C++ hard. Sometimes you   
   > need them for performance, though.   
   >   
      
   I'll answer to this in semi-rant mode, as it seem to be a common theme   
   with C++. (It certainly is common where I work, also when discussing   
   with some friends.):   
      
   And I can't hear it anymore! C++ is a professional tool, and we should   
   use the language to it's full potential, and not limit ourselves to   
   what "everybody understands". The *whole* dang language is "weird and   
   full of restrictions", and still there we are using it, because one or   
   the other reason!   
      
   I mean, who's this Everybody anyway? Is it Alice the Apprentice? Is it   
   Never Change my C-with-classes Ways Noah? Is it Last Programmed C++   
   Years Ago Larry? None of these should have any business dictating how   
   Daily C++ Programmer Donald has to write his code.   
      
   cheers,   
   Martin   
      
   --   
   Good C++ code is better than good C code, but   
   bad C++ can be much, much worse than bad C code.   
      
      
         [ 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)