Home > Articles > Software Development & Management > Object Technology

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

Object Construction/Destruction

The process of initializing and starting up a class is called construction. The opposite of this is the process of tearing down a class and cleaning it up, which is called destruction or finalization. Class construction occurs either when an object is being initialized or upon first reference to a type. Understanding this process helps resolve initialization bugs in complicated object instantiation scenarios.

Another important aspect of object lifetime management is the destruction process. Chapter 1 offered a brief explanation of memory management and garbage collection. Here, we expand on that and bring home the reality of what Common Language Runtime (CLR) memory management means when executing the object destruction/finalization process.

Constructors

Constructors initialize the state of an object. A C# class can have two types of constructors: static and instance. Static constructors (also called type constructors) initialize the state of a type, which is available to all code that accesses that type. Instance constructors initialize the state of each individual object instance.

Before looking at the syntax of static and instance constructors, it is important to understand the difference between static type access and instance access. Upon the first reference to a class, its type is loaded into memory. That type can have static members, which will be available to all code that accesses the type. In contrast, individual instances of a type can be instantiated and referenced as individual objects. Any members of a type that are not marked static are instance members. Instance members are unique for each object of that type that is instantiated. Type members, modified as static, may be accessed through the type identifier. However, instance members are accessed through a variable that the code creates as a reference to an instance of the type. The following sections will illustrate type and instance access.

Static Constructors

A static constructor will initialize type state only one time, when the type is loaded. Although instance constructors have access to static data, they shouldn't ever touch static members. This would corrupt the type state every time an instance was created. Therefore, static constructors are the only solution to initialization of type state. Listing 3.2 shows how to create a static constructor.

Listing 3.2 A Static Constructor (StaticConstructor.cs)

using System;

public class MyStaticClass
{
  public static int StaticInt;

  static MyStaticClass()
  {
   StaticInt = 7;
  }
}

class StaticConstructor
{
  static void Main()
  {
   int myInt = MyStaticClass.StaticInt;

   Console.WriteLine("myInt: {0}", myInt);
   Console.ReadLine();
  }
}

Points to pay attention to in the static constructor in Listing 3.2 are that it begins with the static modifier, does not specify a return type, and the name, MyStaticClass, is the same as its enclosing type name. Static constructors do not take parameters either, and it would not make sense because they are never called explicitly in code. They are executed implicitly the first time a static member of the type is used.

Instance Constructors

The state of each individual instance should be initialized in instance constructors. Listing 3.3 shows how to create an instance constructor.

Listing 3.3 An Instance Constructor (InstanceConstructor.cs)

using System;

public class MyInstanceClass
{
  public int MyInstanceInt;

  public MyInstanceClass()
  {
   MyInstanceInt = 7;
  }
}

class InstanceConstructor
{
  static void Main()
  {
   MyInstanceClass myClass = new MyInstanceClass();

   int myInt = myClass.MyInstanceInt;

   Console.WriteLine("myInt: {0}", myInt);
   Console.ReadLine();
  }
}

Similar to the static constructor, an instance constructor does not return a value and has the same name as its enclosing type. The syntax differences are that there is no static modifier, and instance constructors can accept parameters and be overloaded (different types and number of parameters). Instance constructors also have visibility modifiers (discussed in a later section).

Notice in the Main method that a new instance of MyInstanceClass is being created with the new operator. This is what distinguishes usage of instance from static types, where each individual instance must be explicitly created, but static types are referenced by specifying the type and the static member to access.

Destructors

A C# destructor is a special type member that is invoked when garbage collection occurs and the instance it is a member of is available for collection. Instances become available for collection when there are no more references to them. For example, the instance could go out of scope or be explicitly set to null. The purpose of the destructor is to release unmanaged resources, such as file streams, network connections, or database connections, to name a few. If there are no unmanaged resources to release, a destructor is not necessary.

Because destructors slow down memory management and don't guarantee proper destruction of unmanaged resources, additional measures are necessary to properly manage release of unmanaged resources.

During the garbage collection (GC) process, types with a destructor have to be visited twice. The first pass of the garbage collector (GC) follows roots and identifies objects for garbage collection. If these objects don't have a destructor, they are cleaned up and done. However, objects with a destructor are placed in a temporary queue. This queue is called on a second pass of the GC, so the destructors of the object can be called.

The GC is nondeterministic and can't guarantee when or if a C# destructor will be called. The GC happens when memory pressure forces it into operation. This is by design because just-in-time garbage collection is more efficient in the general case. If a program has a small footprint, it is possible that a GC will never happen at all. Subsequently, multiple unmanaged resources may be held within the type and never released for the life of the program. If the program crashes, destructors will not be called. One would hope that the OS would help recover some of its resources, but this may not occur and such cleanup behavior is not guaranteed by other application or network resources.

The proper way to release unmanaged resources in C# is to implement the dispose pattern in a type. The IDisposable interface (discussed in the "Interfaces" section of Chapter 4) helps implement the dispose pattern. Listing 3.4 describes how to implement a destructor.

Listing 3.4 Destructor Implementation (Destructor.cs)

using System;

public class MyInstanceClass
{
  // some implementation

  ~MyInstanceClass()
  {
   Console.WriteLine("Releasing Resources...");
  }
}

class Destructor
{
  static void Main()
  {
   MyInstanceClass myClass = new MyInstanceClass();

   myClass = null;

   GC.Collect();

   Console.ReadLine();
  }
}

The myClass reference in the Main method of Listing 3.4 is set to null right after it is instantiated. Because there aren't any other references to this instance, setting it to null makes it available for garbage collection. Objects go out of scope and are available for garbage collection if they are allocated in a routine and there are no other references to them. However, while inside a routine, objects remain allocated. This means that long-running routines that allocate many objects increase memory pressure caused by the application and could impact performance. A way to deal with this problem, if logically possible, is by setting objects to null when they are no longer needed. This allows the garbage collector to clean up those objects and work more efficiently. However, if the routine is short and doesn't allocate many objects, setting objects to null doesn't yield much benefit.

Remember that garbage collection occurs in a nondeterministic manner; the destructor can be invoked some time in the future. Syntax for destructors includes the tilde (~) followed by the name of the destructor, which is the same as its enclosing type. Structs do not have destructors, so it is best to ensure that the disposable pattern, described in the "Interfaces" section of Chapter 4, is implemented.

A Struct Is a Custom Value Type

You can create your own custom value types, similar to the way reference types are created with class definitions. When creating a custom value type, declare the type with the struct keyword as shown following:

public struct complex
{
  double real;
  double imaginary;

  // implementation omitted
}

This struct may be declared as

complex myComplexNumber = new complex();

or

complex myComplexNumber;

You would create a struct when value type semantics are required. In addition to being allocated on the stack and contents being copied during assignment, a struct does not have a default (no parameter) constructor and does not have a destructor. This is because structs are automatically initialized with integral types set to 0, floating-point types set to 0.0, bool types set to false, and string and other reference type members set to null. Structs do not inherit other types and may not be inherited from. An exception is that structs may inherit interfaces (discussed later). Other than these differences, structs are used like classes and are manipulated as permitted by the public members they expose.

The Main method of Listing 3.4 calls GC.Collect to force a garbage collection. You shouldn't call GC.Collect yourself unless you are absolutely sure that there is a benefit. The garbage collector is optimized to provide better performance than most developers can achieve themselves, and calling GC.Collect is more likely to hurt performance. The reason this example calls GC.Collect is that the destructor in myClass would never be called if the program was left running. Recall that the garbage collector is optimized to do a garbage collection only when memory pressure forces it to do so.

Now consider the case where the call to GC.Collect was deleted or commented out. Because this program is so small, there will never be any memory pressure or other implicit event to force the garbage collection, meaning that the destructor will never be executed until the program exits. You can start this program and go get a cup of coffee, go out for dinner, or even go on vacation and that destructor will not be called. The section on interfaces in Chapter 4 will show how to fix this problem.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020