Home > Articles > Programming > General Programming/Other Languages

This chapter is from the book

This chapter is from the book


Typecasts can be used to coerce a type declared one way to be treated as some other type that descends from it. For instance, in the following code a typecast is used to enable an object declared as type TPersistent to be treated as a TStringList:

procedure TForm1.Button2Click(Sender: TObject);
  F: TPersistent;
  L: TStringList;
  L := TStringList(F);

You perform a typecast by stating the name of the type that you want to declare and then placing the object that you want to typecast in parenthesis. The compiler is smart enough to know that this is a typecast, not a function call. The user can often make the same deduction simply by seeing that TStringList begins with the telltale T, which stands for "type." That particular initial consonant gives away the fact that TStringList is a type, not a function.

The as and is Operators and the Sender Parameter

Typecasts are an essential part of working with a language that supports polymorphism. In many Kylix programs, the IDE generates event handlers that are passed objects declared to be one type but that are actually descendants of the type passed. The classic example of this is the Sender parameter, seen in many event handlers:

procedure TForm1.Button1Click(Sender: TObject);


The Button1Click method in a typical Delphi application is called when the user clicks on Button1. In that case, the Sender parameter really contains a TButton object. Flexibility is gained, however, if you declare the parameter as a TObject. The declaration enables you to pass any Pascal object to this method, not just a TButton.


All Object Pascal classes must descend from TObject or one of its descendants. Even if you declare an object to have no ancestor, the Pascal compiler automatically descends the class from TObject. You simply can't declare an Object Pascal class that does not descend from TObject or one of its descendants. As a result of this rule, it is legal to pass any object in the Sender parameter of the Button1Click method. This extraordinary flexibility is possible because all these objects, by definition, descend from TObject.

Let's look at a practical example of how declaring the Button1Click method to take a TObject might be useful in a real program. Imagine that a message handler that you want to respond to clicks on not only a TButton, but also a TBitButton and TSpeedButton. The previous declaration could work with any of those types because they are all descendants of TObject. More particularly, the magic of polymorphism grants TButton, TBitButton, or TSpeedButton the capability to masquerade as a lowly TObject.


Never forget the hierarchical nature of polymorphism: The king can masquerade as a pawn, but a pawn cannot pretend to be a king. A TButton can go disguised as a TObject, but a TObject cannot put on airs and pretend to be a TButton.

Here is how you can get at the object passed in the Sender parameter:

procedure TForm1.Button1Click(Sender: TObject);
  Button: TButton;
  Button := TButton(Sender);

As you can see, you need do nothing more than perform a simple typecast, and the Sender object is uncloaked and its true nature as an instance of TButton is revealed. In this case, the typecast again plays the role of the truth-teller, stripping off the object's disguise.

But doesn't trouble lurk amid the players of this game of cat and mouse? What would happen if the truth-teller were wrong? If you typecast a Sender object as a TButton, but it was really a TBitButton, TSpeedButton, TPanel, or something else passed unexpectedly, your typecast would be allowed at compile time, but an exception would be raised at runtime. Here is what you can do in such cases:

procedure TForm1.Button1Click(Sender: TObject);
  Button: TButton;
  if Sender is TButton then
    Button := TButton(Sender);

This code uses the is operator to test whether Sender is of type TButton. If it is, the if statement evaluates to true and the call succeeds. If it is not, the second line attempting the typecast is never called.

There is another way to perform a typecast that is perhaps a bit more modern than the way I have shown you so far:

procedure TForm1.Button1Click(Sender: TObject);
  Button: TButton;
  Button := Sender as TButton;

This code yields that same result as writing Button := TButton(Sender). The difference is that the code will raise an exception if Sender is not of type TButton. The as operator is a prophylactic ensuring that the typecast will not be made if it is not valid. I also find the code easy to read because it cannot be mistaken as a method call, per the discussion earlier in this section. On the other hand, the code might take longer to execute than the other kind of typecast because it is adding the overhead of type checking. (An actual ruling on the performance of the two forms of typecasts will have to be left to someone else because I am not an expert in this kind of performance issue. But certainly the additional type checking must add at least some overhead to your program.)

The as operator is most typically used in statements that look like this:

procedure TForm1.Button2Click(Sender: TObject);
  F: TPersistent;
  L: TStringList;
  (F as TStringList).Add(`Sam');

Here you can see the way parentheses have been added to give precedence to the as operator and ensure that the compiler can make proper sense of your statement.

Hopefully you now understand the basics of how typecasts work in an Object Pascal program. If you still feel that you could use more enlightenment on this issue, just be patient—the subject will come up numerous times throughout the course of this book.

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.


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.


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.


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.


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


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


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.


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.


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