Have an amazing solution built in RAD Studio? Let us know. Looking for discounts? Visit our Special Offers page!
CodeDelphiTech Partner

What Are The Mistakes We Made In Creating Delphi Objects?

001-reflection-on

Practically every developer, even a newcomer in programming, can create and destroy objects correctly. A classic construction that is used in the majority of programs looks the following way:

Yet, some time ago, there were a lot of discussions where to place object creation: before an exception handler or within the try-finally-end construction. Of course, now, it is not difficult to find an answer to this question. An example of well-written code can be found on many online resources, such as StackOverflow, in books and in official documentation.

But do you really understand why it is so and what can happen if you use the wrong variant? It is possible that you will have to answer this question during a technical interview. If you do not know the correct answer, just keep reading this article!

What is the best way to debug a Delphi code problem?

You can get debug messages in various ways, but one of the most convenient is to use the CodeSite logging system. You can install the ‘lite’ version from GetIt Package Manager using this link: https://getitnow.embarcadero.com/?q=codesite&product=rad-studio&sub=all&sortby=date&categories=-1


What is the wrong way to use an object?

As an example, let’s create a class.

In our class we will redefine the Free method only for having a look at the address of the object that we want to destroy. We will copy the code that will destroy the object from the Free method of the TObject class. The only unique method will be getSelfPointer that returns the Pointer to the Object.
The class constructor as a parameter will have a logical meaning. If it equals True, an exception will be generated and an object won’t be created.
Now, let’s take two global variables of the TMyClass type.

How do we get an error in a Delphi constructor?

Then let’s place two buttons on the form and define click handlers for them.

To begin with, we create an object MyObject and put its address in the memory to the log and immediately destroy it. Then we create MyObject2, check its address in the log and then create MyObject again. At the same time, we generate an exception in the constructor. Actually, this object won’t be created.

According to the official documentation – https://docwiki.embarcadero.com/RADStudio/Sydney/en/Methods_(Delphi)– “If an exception is raised during execution of a constructor that was invoked on a class reference, the Destroy destructor is automatically called to destroy the unfinished object“.

As a result of the code execution, in the log we see the following:

At the very beginning, MyObject is created and then it is immediately destroyed. Then MyObject2 is created. And here’s where we have the first surprise. The address of a new object is fully identical to the address of the object that has been destroyed. But, actually, there is nothing unexpected given the peculiarities of how the object storage is organized in Delphi.

Then we need to bear in mind that though the Free method destroys an object, it doesn’t destroy the link that leads to it.
In other words, MyObject won’t be equal to nil.

What happens during the creation of an object placed inside the exception handler?

What happens if now during the creation of the object placed inside the exception handler, an error will arise? You are right, the finally block will be executed and the Free method will be called.

We are talking about this part of the code:

We remember that the object won’t be created. But a static method Free will consider that the object is still available at the address 018A8B80 as the link after the first creation of the object is stored. But in reality that’s the address of another object which will be destroyed. To make sure that it is so, it is enough just to press Button2.

We will get a well-known Access Violation error.

As a result, due to using this construction for creating and destroying an object, we have destroyed another object. Similar errors are quite dangerous when it comes to lists of objects. And the search for such errors is a rather challenging process. It is obvious that nothing of this kind happens if we create MyObject for the second time in a way that is applied in the majority of cases.

Where can I read more on access violations, Delphi objects, and classes?

For a deeper understanding of the information, I recommend reading the following article http://rvelthuis.de/articles/articles-pointers.html, as well as the materials provided by Aleksandr Alekseev https://www.gunsmoker.ru/2009/04/freeandnil-free.html


This article was written by an Embarcadero Tech Partner. For more articles by Softacom and our other Tech Partners click the following link: https://blogs.embarcadero.com/category/tech-partner/


What's New for RAD Studio 11

Reduce development time and get to market faster with RAD Studio, Delphi, or C++Builder.
Design. Code. Compile. Deploy.
Start Free Trial   Upgrade Today

   Free Delphi Community Edition   Free C++Builder Community Edition

Related posts
C++CodeDelphiIDERAD Studio

New Platform Identifiers in RAD Studio, Delphi and C++Builder 11 Alexandria

NewsWhitepaper

The Pros And Cons Of Artificial Intelligence

C++DelphiRAD Studio

9 Signs You Should Invest in Automation

C++DelphiNewsRAD StudioWhitepaper

A Beginner’s Guide to Artificial Intelligence

3 Comments

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

IN THE ARTICLES