It is much more expensive than analysing _LastError.
Unfortunately, lost the universality by introducing macros with different number of input parameters. There may be problems with non-standard properties.
It is much more expensive than analysing _LastError.
Unfortunately, lost the universality by introducing macros with different number of input parameters. There may be problems with non-standard properties.
These are one-time helpers not a time-critical code. it does not make any difference for the user if it took 10 nansosec vs 100 nanosec :)
I don't give a shit for my cpu usage / electricity bill.
It's already documented. Don't mix pools of history from different sources.
Just trying to use your function.
// Пробуем распечатать все балансовые сделки.voidOnStart()
{
if (HistorySelect(0, INT_MAX))
for (uint i = HistoryDealsTotal(); (bool)i--;)
{
constulong Ticket = HistoryDealGetTicket(i);
if (HistoryDealGetInteger(Ticket, DEAL_TYPE) == DEAL_TYPE_BALANCE)
PrintDeal(Ticket);
}
}
In short, I pointed out an architectural error and gave an example of its manifestation. The error will not disappear from the results of the discussion.
In short, I pointed out an architectural error and gave an example of its manifestation. The error will not disappear from the results of the discussion.
Please, if you make mistakes in code in this thread, correct them instead of exercising wit.
My friend if you find the code is not fitting your needs then you can skip it, this is up to you.
There are no mistakes in my code, the mistakes are actually in the way to you try to fit the function into a situation that is actually documented on the platform documentations page.
FYI, it is the job of forum's admin to decide for users what to post or not on this thread.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Here is the result from PrintEnum<ENUM_TIMEFRAMES>();
output:
Forum on trading, automated trading systems and testing trading strategies
Peculiarities of mql5 language, subtleties and techniques of work
amrali, 2025.02.14 05:37
It is much more expensive than analysing _LastError.
Unfortunately, lost the universality by introducing macros with different number of input parameters. There may be problems with non-standard properties.
It is much more expensive than analysing _LastError.
Unfortunately, lost the universality by introducing macros with different number of input parameters. There may be problems with non-standard properties.
These are one-time helpers not a time-critical code. it does not make any difference for the user if it took 10 nansosec vs 100 nanosec :)
I don't give a shit for my cpu usage / electricity bill.These are one-time helpers, not time-critical code. It makes no difference to the user whether it took 10 nanoseconds vs 100 nanoseconds :)
Why make it sub-optimal?
It is already documented. Do not mix history pools from different sources.
It's already documented. Don't mix pools of history from different sources.
Just trying to use your function.
In short, I pointed out an architectural error and gave an example of its manifestation. The error will not disappear from the results of the discussion.
Just trying to use your function.
In short, I pointed out an architectural error and gave an example of its manifestation. The error will not disappear from the results of the discussion.
Then remember to rename my function to:
Please, if you make mistakes in code in this thread, correct them instead of exercising wit.
Please, if you make mistakes in code in this thread, correct them instead of exercising wit.
Readers are kindly requested to comment.