Hi KURT,
KURT KUZBA was observed on 14-Sep-97, writing to ROGER SCUDDER
          Something about: Worked this out
RS>> KK>   class MathCalc
RS>> KK>   {
RS>> KK>   private:
RS>> KK>      int iVar1, iVar2, iResult;
RS>>   Why do you code the private keyword when the data is
RS>>   private by default.  Is this considered good style?
 KK>    I don't know, really. It's just something I picked up.
 KK>    I always put the public functions at the top of the class
 KK>    and then put in the private members later, which means I
 KK>    have to specify that they are private.
  But in this case you didn't place public data at the top.
  You did exactly what is above, which is place private
  members at the top.  My question is, if the data is private
  and it is at the top, before any access specifiers, why
  would you place a private tag before it, when the access
  is already private by default?
  I am not singling you out. I have seen several other
  people do that.  Really it's not that important to me
  to know why you did it.  I think the important thing is
  that one knows the difference.
 Roger Scudder
 rogers@gim.net
... 'If it ain't broke, you can probably still fix it.' - Tim Allen
--- Terminate 5.00/Pro 
 * TerMail/QWK * Terminate = Pointmailer+Tosser+Reader+Packer+QWK!
--- WILDMAIL!/WC v4.12 
---------------