Arguably, you could say this applies to c/c++ as well, because windows or the OS destroys the process space. Still you will accumulate used memory over time, if you keep repeating this.
It's not a garbage collecting language like java. We, the coders do have to take care of such issues, and we should clean up, and not rely on the platform to do it for us. Especially when a software is running for prolonged time.
Of course you are right. But it's really hard to have such memory leak with MT4/MT5 when you get messages in the logs about them, I am not able to name that memory leak. You practically have to do it on purpose.
The point is there is no valid reason to not use pointers in MQL.
Of course you are right. But it's really hard to have such memory leak with MT4/MT5 when you get messages in the logs about them, I am not able to name that memory leak. You practically have to do it on purpose.
The point is there is no valid reason to not use pointers in MQL.
Yes, I agree. I myself make use of mql "pointers" a lot and I think they are very helpful and flexible, especially compared to structs.
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.
Of course you are right. But it's really hard to have such memory leak with MT4/MT5 when you get messages in the logs about them, I am not able to name that memory leak. You practically have to do it on purpose.
The point is there is no valid reason to not use pointers in MQL.
Of course you are right. But it's really hard to have such memory leak with MT4/MT5 when you get messages in the logs about them, I am not able to name that memory leak. You practically have to do it on purpose.
The point is there is no valid reason to not use pointers in MQL.