-----------------------------------------------------------

New Message on BDOTNET

-----------------------------------------------------------
From: nitin_karan
Message 2 in Discussion

Hi,   Look at the copy constructor sample :   using System; namespace 
CopyConstructorSample
{
 /// <summary>
 /// Summary description for CopyConstructor.
 /// </summary>
 public class CopyConstructor
 {
  public int var1;
  public CopyConstructor()
  {}   public CopyConstructor(CopyConstructor obj)
  {
   var1 = obj.var1;
  }
 }
}
 However consider the following points before using them :   1.       Favor Clone and 
Deserialize over copy constructors unless you�re really aiming at value semantics. 
They will be more consistent with the way serialization works and the existing 
patterns. 2.       It�s easy to implement a Clone method in terms of a copy 
constructor and impossible to do the opposite, but� 3.       Object.MemberwiseClone 
supports writing Clone methods and not copy constructors. 4.       Like many things in 
the pre-generics flavor of C#, the �object� return type of ICloneable.Clone is 
unfortunate, but just deal with it. 5.       Don�t overlook using serialization if you 
just need some kind of copy operation.   --Nitin    

-----------------------------------------------------------

To stop getting this e-mail, or change how often it arrives, go to your E-mail 
Settings.
http://groups.msn.com/bdotnet/_emailsettings.msnw

Need help? If you've forgotten your password, please go to Passport Member Services.
http://groups.msn.com/_passportredir.msnw?ppmprop=help

For other questions or feedback, go to our Contact Us page.
http://groups.msn.com/contact

If you do not want to receive future e-mail from this MSN group, or if you received 
this message by mistake, please click the "Remove" link below. On the pre-addressed 
e-mail message that opens, simply click "Send". Your e-mail address will be deleted 
from this group's mailing list.
mailto:[EMAIL PROTECTED]

Reply via email to