Publishers of technology books, eBooks, and videos for creative people

Home > Articles

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

Class Constructors

Constructors allow you to define a method signature with the required arguments to instantiate a new object of a specific type.

Dart has support for “zero argument constructors.” You may have noticed that Example 4.5 didn’t define a constructor method, or a superclass. Let’s modify the Airplane class (as shown in Example 4.7) to be a bit more customizable upon instantiation:

EXAMPLE 4.7

class Airplane
{
  static const double bodyWeight = 1000.00;
  static const double fuelCapacity = 100.50;

  String color;
  String wing;
  int seatCount;

  Airplane(int seatCount, String color, String wing) {
    this.seatCount = seatCount;
    this.color  = color;
    this.wing = wing;
  }

  double getWeight() {
    return bodyWeight + seatCount + fuelCapacity;
  }
}

main() { //new scope
  Airplane yourPlane = new Airplane(1, "White", "Fixed");
  Airplane myPlane = new Airplane(2, "Gold", "Triangle");
  print( 'yourplane weight:'+ yourPlane.getWeight().toString() );
  print( 'myplane weight: '+ myPlane.getWeight().toString() );
}

//Output:
//yourplane weight: 1101.5
//myplane weight: 1102.5

Generative Constructor

Example 4.7 appended a named Airplane constructor function that accepts three arguments using standard comma-delimited parameters. The Airplane() constructor function matches the name of the Airplane class. This is referred to as a generative constructor. The hardcoded values for color, wing, or seatCount are gone. Instead of hardcoded values, the constructor requires that the class fields be assigned by the arguments that are passed in upon instantiation.

Automatic Class Member Variable Initialization

If you’ll notice, it’s not very DRY (Don’t Repeat Yourself) to have objects passed into the constructor and then immediately assign them to class fields. If you’re going to automatically assign an argument value to a class field, Dart encourages you to use the keyword this inside the method signature. You can refactor the constructor as shown in Example 4.8.

EXAMPLE 4.8

class Airplane
{
  static const double bodyWeight = 1000.00;
  static const double fuelCapacity = 100.50;

  String color;
  String wing;
  int seatCount;

  Airplane(int this.seatCount, String this.color, String this.wing) {
    // You can leave off the { } altogether
    // This whole block becomes optional
}

  double getWeight() {
    return bodyWeight + seatCount + fuelCapacity;
  }
}

main() { //new scope
  Airplane yourPlane = new Airplane(1, "White", "Fixed");
  Airplane myPlane = new Airplane(2, "Gold", "Triangle");
  print( 'yourplane weight:'+ yourPlane.getWeight().toString() );
  print( 'myplane weight: '+ myPlane.getWeight().toString() );
}

//Output:
//yourplane weight: 1101.5
//myplane weight: 1102.5

Named Constructors

Named constructors replace the practice of default overriding and offer multiple ways to initialize the same class of object.

Example 4.8 created an Airplane object that is initialized with three optional fields. Let’s say you have a different, recurring use case that always has the same wing type and color, but requires a changing seat value. You have older dependencies that require the previous implementation, so let’s add a named constructor for the specific type of Airplane as follows:

EXAMPLE 4.9

class Airplane
{
  static const double bodyWeight = 1000.00;
  static const double fuelCapacity = 100.50;

  String color;
  String wing;
  int seatCount;

  Airplane(int this.seatCount, String this.color, String this.wing);

  Airplane.sparrow(int this.seatCount){
    wing = "Swept";
    color = "Gold";
  }

  Airplane.robin(String this.color){
    seatCount = 1;
    wing = "Swept";
  }

  double getWeight() {
    return bodyWeight + seatCount + fuelCapacity;
  }
}

main() { //new scope
  Airplane yourPlane = new Airplane(1, "White", "Fixed");
  Airplane myPlane = new Airplane(2, "Gold", "Triangle");

  Airplane brothersPlane = new Airplane.sparrow(10);
  Airplane sistersPlane = new Airplane.robin('red');

  print( 'yourplane weight:'+ yourPlane.getWeight().toString() );
  print( 'myplane weight: '+ myPlane.getWeight().toString() );

  print( 'brothersPlane weight: '+ brothersPlane.getWeight().toString() );
  print( 'sistersPlane color: '+ sistersPlane.color );
}

//Output:
//yourplane weight:1101.5
//myplane weight: 1102.5
//brothersPlane weight: 1110.5
//sistersPlane color: Red

Example 4.9 adds a named constructor of Airplane.sparrow to the class. It’s using automatic initialization to assign the this.seatCount parameter. The constructor’s function block has hardcoded assignments for the class’s fields.

main() then instantiates a local variable named brothersPlane by leveraging the named constructor sparrow and the new keyword. All Airplane instances returned by Airplane.sparrow will have swept wings and a color of gold. The only argument accepted by the named constructor sparrow is a numeric value to increase the seat count.

A similar pattern is repeated for the named constructor robin and the variable instance sistersPlane. But in the case of robin, the constructor handles building single-seat airplanes of varying colors.

Factory Constructors

To understand a factory constructor, it’s important to understand that when a generative constructor is invoked, a new object instance is created in memory. For performance reasons, this can be a bad approach to acquiring objects. A common pattern to enforce object reuse is the pooling pattern.

In a pooling implementation, instead of creating a new object in memory on every request, the pattern requires a small group of objects to be created at run time. When a new pool member object is needed, it’s retrieved from the pool. Then, instead of destroying each instance, the unused object is returned to the pool for later reuse.

Factory constructor functions allow you to bypass the default object instantiation process and return an object instance in some other way. You could return an object from memory or use a different approach to initialization. Factories are intentionally flexible.

Factories offload object creation into the factory function’s statement while allowing the signature of the instantiator to use the familiar new NameOfClass() syntax. Let’s compare using a generative constructor against a factory constructor for class Pool():

class Pool
{
   Pool() {
   //do nothing for the generative constructor
   //results in a new object instance
  }
}

main() {
  Pool aPool = new Pool();
  print('aPool: ' + aPool.toString() ); //aPool: Instance of 'Pool'
}

Prefixing the existing constructor declaration with the keyword of factory will show the power of the factory pattern. With a factory constructor in place, you bypass object creation. Let’s take a look:

class Pool
{
   factory Pool() {
    //do nothing in the factory constructor – you'd usually return something
  }
}

Note that the calling implementation does not change, but instead of an instance, you get null:

main() {
  Pool aPool = new Pool();
  print('aPool: ' + aPool.toString() ); //aPool: null
}

Let’s rig up a fake Pool implementation. For the sake of brevity, this pool will always return a new Pool instance:

class Pool
{
  factory Pool() {
    //a pool usually checks for previously constructed objects in cache
    //if we had a cached item, we'd return it, but instead, for brevity,
    //we'll build a new one using a named constructor
    return new Pool.NamedPoolConstructor();
  }

  Pool.NamedPoolConstructor();
}

This will result in an instance of Pool in main(). It uses the named constructor functionality from earlier to return a new instance.

Regardless of what the constructor statement actually looks like, factory constructors and generative constructors provide a consistent interface for acquiring an object using the new NameOfClass() syntax.

Static Variables

A static variable is an object that exists on the class definition and not on the object instance. If your current scope has a class in the namespace, you can access the static variable on the class. The value of the static variable can be modified (Example 4.10).

EXAMPLE 4.10

class Tool
{
  static List collection = ['wrench', 'saw', 'hammer'];
}

main() {
  Tool.collection.add('socket');

  Tool.collection.forEach( (String item){
    print('Collection Has A: $item');
  } );
}

// Output:
// Collection Has A: wrench
// Collection Has A: saw
// Collection Has A: hammer
// Collection Has A: socket

Rather than instantiate an instance of Tool, you simply access the static variable associated with the class Tool.

Final Variables

A final variable can receive only a single run-time assignment. Its assignment must occur upon declaration if being assigned at run time. Once a value is assigned, it cannot be changed. If it’s a primitive value, the primitive value is, in practice, immutable. If it’s an object like a List, the variable’s reference cannot be changed, but the referenced object’s fields are mutable. Final variables can also be declared as static like any other variable.

EXAMPLE 4.11

class Runway
{
  final String item = "Asphalt";
  final List materials = ["Asphalt", "Gravel", "Cement"];
}

main() {
  Runway rw = new Runway();

  //primitives
  print(rw.item); //prints Asphalt
  rw.item = "Concrete"; //Error 'item' cannot be used as a setter, its final

  //object
  rw.materials.add('Sand'); //adds 'Sand' to the List and modifies its value
  rw.materials = ['Steel']; //Error 'Runway' has no instance setter...
}

In Example 4.11, you can access the value of String item, but you cannot change the reference of String item to a different string, because that would be a second assignment.

You can add() another object to List materials, or use any of its instance methods, as long as you do not assign a new reference to the final variable. The assignment of a List literal to the final variable encounters the same restriction as in the string example: no secondary assignments allowed.

  • + Share This
  • 🔖 Save To Your Account

Peachpit Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Peachpit 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 Peachpit 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 ask@peachpit.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 Adobe Press. 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.peachpit.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