I'd like the opinion of the folks in this echo concerning the 
following statement from the book "Black Belt C++..." 
 
`` 
C programmers are faced with two temptations in writing 
constructors: 
 
     o    The temptation to ascribe too much responsibility to 
          the constructor.  The constructor's responsibility is 
          to "make an object out of a bunch of raw bits."  Just 
          that, and no more.  A constructor that has sweeping 
          side effects is normally poor programming practice 
          because constructors can be called by the compiler 
          when you least expect it.  This can introduce exposure 
          to buggy behavior or inefficiency. 
 
     o    The temptation to write a constructor to create an 
          object of a user defined type from just about any 
          other type imaginable.  Conversion by construction is 
          not bad, but it is important to define what sort of 
          conversions make sense up front. 
'' 
 
How would you define "ascribing to much responsibility to the 
constructor?"  Is this to much... 
 
 
manifest::manifest(){ 
     filename = new char[FILENAME_MAX]; 
     while (!select(filename, FILENAME_MAX - 1)); 
     mstreamp = new ifstream(filename); 
} 
 
 
*What color is a chameleon on a mirror? 
 
e-mail:  benjamin.l.mcgee@purgatoire.org 
NET-MAIL: Benjamin L McGee on 1:15/7
--- FLAME v1.1
---------------