
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Add.
I added ))
For a circle it is calculated one way, for a square another. But in either case - by calling Figura.GetSquare(),
And silence ...
Well, it was a 2x2=?
Not interested in answering.
=================
Maybe this is closer.
There is a standard set of virtual methods in a class: Open(), Close(), Read(), Write() etc.
Such class can handle files, mapping, channels, internet, etc.
Only the contents (description) of these methods will differ. But the class interface will be identical.
Don't you think it's suspicious that it's already the 3rd page on the subject and no one cited a single code point as an example?
Besides, it's not interesting to answer, it's elementary, it's so simple that it's too lazy to code...
If someone knew something, I think they would have answered...
VOLDEMAR, if you take your first post, why is there a class there at all? Writing classes is a consequence of program complexity, when individual elements have many external links, then a class is created to unite all these elements and create a simple interface. In my opinion, a necessary attribute of a class is data (int's, double's ...) - material with which functions work, the class connects all in one package (data and functions).I think this is the basic idea of OOP. For example, two examples, first without OOP, second with it:
In the second example, we don't have to worry about data that functions will work with, I think this is the main purpose of OOP.
One more comment about your code:
... class vr_trade { ... ~vr_trade(){} }; ...
I have a rule: never write a destructor empty. The absence of a destructor is an indicator of class simplicity. If a destructor is written, you may have to write a copy constructor and the = operator or forbid them. Example:
This will cause delete to be called twice for the same pointer. The correct way is this
So, if you have to write a destructor, it's a good reason to think twice - what to do with opera = and copy constructor? Delete it, write it...? I don't think you should write destructor empty, its absence is an indicator that you don't need to redo the above.
Why does the second method throw a bunch of errors and warnings ???
Put a dot after this instead of ->. mql chip.
Please explain the actions
namely
why the sign (:) and what do we get with it?