Discussing the article: "Developing a Replay System (Part 29): Expert Advisor project — C_Mouse class (III)"

[MetaQuotes]

Check out the new article: Developing a Replay System (Part 29): Expert Advisor project — C_Mouse class (III).

After improving the C_Mouse class, we can focus on creating a class designed to create a completely new framework fr our analysis. We will not use inheritance or polymorphism to create this new class. Instead, we will change, or better said, add new objects to the price line. That's what we will do in this article. In the next one, we will look at how to change the analysis. All this will be done without changing the code of the C_Mouse class. Well, actually, it would be easier to achieve this using inheritance or polymorphism. However, there are other methods to achieve the same result.

But let's get to what brought us to this article. Here we will look at how, without changing the class and without using the inheritance system, to extend the capabilities of the system in a controlled, safe and reliable way, regardless of ability. The task may seem simple at first, but it will provide a deeper understanding of how things work, far beyond what we get when we build the same method every time.

In today's article we will look at a way to expand the financial instrument analysis system. We'll use the C_Mouse class along with what it inherits from the C_Terminal class to create another analysis niche. However, we will do this in a rather interesting way: we will create a new class that will use the contents of the C_Mouse class, but without directly inheriting from it. This new class may or may not then be added to the final code, depending on our goals. But regardless of this, we will learn how to create our own training model without violating the integrity of the previously created and tested code. This is the real purpose of this article.

Author: Daniel Jose