Is it common for code to "change on its own" after being idle for a long time?

New comment
 
Is it common for code to "change on its own" after being idle for a long time?

Whenever I make a new update, I create a new version of this code, thus generating several versions (1.01, 1.02, 1.03... etc)... and I keep them saved for future reference.

The problem is when I go to check later and the code either no longer compiles or no longer works as before.

What problems could be occurring?
 
Samuel Cavalcanti Costa:
Is it common for code to "change on its own" after being idle for a long time?

Whenever I make a new update, I create a new version of this code, thus generating several versions (1.01, 1.02, 1.03... etc)... and I keep them saved for future reference.

The problem is when I go to check later and the code either no longer compiles or no longer works as before.

What problems could be occurring?
Most likely this is bacause of MQL5 is constantly changing, which in many cases breaks back-compatibility.
 
Stanislav Korotky #:
Most likely this is bacause of MQL5 is constantly changing, which in many cases breaks back-compatibility.
So what do you suggest regarding the codes passed? Just a lookup?
 
Samuel Cavalcanti Costa #:
So what do you suggest regarding the codes passed? Just a lookup?
Fix it according to the last compiler. This usually takes 5 minutes even on a very large codebase.
 
Alain Verleyen #:
Fix it according to the last compiler. This usually takes 5 minutes even on a very large codebase.
Got it
 
Which errors is your code showing?
 
Osmar Sandoval Espinosa #:
Which errors is your code showing?
The code simply stops working. Even backtesting doesn't pick it up anymore... the older/more forgotten the code is, the harder it is to get it working. In the end, they only serve as a reference for future code.

But then I discovered that there are external interferences that degrade the code. I need to find a safer way to store my code.
New comment