I don't agree. Showing how he writes his own library, helps the user develop that skill. It helps the user know and understand the underlying functions in MQL that are used to develop the libraries.
I don't agree. Showing how he writes his own library, helps the user develop that skill. It helps the user know and understand the underlying functions in MQL that are used to develop the libraries.
I write my own classes when needed but mostly a code using the MQL functions directly.
sorry i didn't mean any disrespect. i didn't mean to say counterproductive in the way that it's useless that's why i asked whether he means to show us the logic behind it or that he just wants us to use his library. if it's the former, then the same can be achieved by showing us how the standard library is written. i guess i just don't like not knowing the direction he's going. i don't mind learning but i would feel a lot better if he could be clearer in the beginning (or maybe he would, i still haven't finished the book). it also feels redundant because i will still need to learn the standard library. however it's all fine anyway because i like the book's structure and it realy helps to demistify the process. but honestly, if he means for us to not use the standad library, wouldn't that be like...not the best thing? like why would anyone go through that? idk
anyway thank you very much for the reply.
anyway thank you very much for the reply.
Many users, like myself, don't use and don't like using the Standard Library, mainly because we find it awkward and slightly "buggy" in a sense.
Also, not everyone is a fan of heavy Object-oriented programming (OOP) usage. Many, like myself, use OOP sparingly.
At the time that the book was written, it was quite bad, in my opinion.
It has improved substantially over time however, but personally, I prefer not to use it.
I would rather rely on my own libraries.
The Standard Library obviously.
I would not consider the library in the book bad at all. It is, however, somewhat outdated now, since a book cannot undergo continuos "updates" to reflect newer developments of the platform.
Yes, but only after you have finished the book and have researched the changes and updates the platform has undergone to date.
Alternatively, stick to non-OOP approach in the beginning. For most of the tasks, especially indicator development, there is no need to overcomplicate things with OOP.
Almost all of my EAs use no OOP at all and the more complex ones use minimal and simplistic OOP.
We are not talking about "grand" applications with complex UI/UX. EAs should be simple and efficient, focusing on the trading, with minimum or no visual distractions for the user.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
in his book that teaches MQL5, he taught readers using his own library, where he has his own trade class functions.
Isn’t better to just use the standard library?
does he only mean to teach us the logic behind the class functions? or does he really want us to use his library/make up own?
i feel like this is so counterproductive.
do you guys use the standard library or andrew young’s library?