Defending every division is going to be a very long task.
One thing I have seen recommended is when building the code, to include print statements (to display or log file) for potential problem areas that output either what variable you are expecting back from a certain thing, and what variable is actually being used by the program. Then, after all testing is done, comment them out. It is extra work, but it can help you find a troubled spot. Since your code is so large now, obviously, this would not be feasible, but at least go to the spot you think is most likely. Hopefully you will be able to track it down relatively quickly.
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.
My total code length runs beyond 27000+ lines.
Defending every division is going to be a very long task.
My total code length runs beyond 27000+ lines.
Defending every division is going to be a very long task.
Are you sure it's not 2700 ? i do not think the compiler will handle 27000 easily.
you either make it work of fail.
if you coded it in a specific way you can use find and replace / replace all.
Are you sure it's not 2700 ? i do not think the compiler will handle 27000 easily.
you either make it work of fail.
if you coded it in a specific way you can use find and replace / replace all.
what's the file size after that?