Discussing the article: "From Novice to Expert: Collaborative Debugging in MQL5"
Good article for beginners, a bit verbose in my opinion. Some remarks :
- You should clearly say that when you have a list of errors, you ALWAYS need to start checking the first one at the top of the list. This is the most efficient way to deal with errors and to avoid wasting time with secondary errors.
- You should provide the "buggy" version of the "D1_PriceMarker.mq5", so people will be able to practice themselves following your article.
ObjectSetInteger(0, labelName, OBJPROP_YDISTANCE, price); // Position label at the price level
- This is clearly a logical error, an 'Y_DISTANCE' is an integer value (pixel position on the screen) and you provided a double 'price'.
Engaging in discussions about coding challenges is a fantastic way to learn from other experts.
- I barely have seen you active on the forum, either to ask or answer questions.
Collaborative Debugging in MQL5
- I don't get it. Where is the "collaborative part" ? Did I missed something.
Hello.
Good article for beginners, a bit verbose in my opinion. Some remarks :
- You should clearly say that when you have a list of errors, you ALWAYS need to start checking the first one at the top of the list. This is the most efficient way to deal with errors and to avoid wasting time with secondary errors.
- You should provide the "buggy" version of the "D1_PriceMarker.mq5", so people will be able to practice themselves following your article.
- This is clearly a logical error, an 'Y_DISTANCE' is an integer value (pixel position on the screen) and you provided a double 'price'.
- I barely have seen you active on the forum, either to ask or answer questions.
- I don't get it. Where is the "collaborative part" ? Did I missed something.
Thank you for your feedback, Alain Verleyen! I genuinely appreciate your insights, particularly as a moderator, and I agree that clarity is essential, especially for beginners.
- You're absolutely right about the importance of addressing the first error on the list.
- That's an excellent suggestion! While I didn't include the source file in the article, readers can find and copy the "buggy" version of the "D1_PriceMarker.mq5" at this link.
- Thank you for pointing out the logical error regarding Y_DISTANCE .
-
Regarding the collaborative aspect, my intention was to encourage readers to engage with each other in the comments or on the forum to share their own debugging experiences and solutions. I will work on improving my visibility on the forum.
I truly value your constructive criticism and engagement! Discussions like this are vital for our collective growth and improvement.
- www.mql5.com
Good morning
What algo traders may not realize.
This is they will spend very little time coding miracle indicators or prodigiously profitable EAs.
The reality is that they will mainly spend time correcting, improving their codes and therefore debugging.
If they don't have powerful tools, they will quickly spend days, which would already be good, looking for their code errors.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Check out the new article: From Novice to Expert: Collaborative Debugging in MQL5.
Problem-solving can establish a concise routine for mastering complex skills, such as programming in MQL5. This approach allows you to concentrate on solving problems while simultaneously developing your skills. The more problems you tackle, the more advanced expertise is transferred to your brain. Personally, I believe that debugging is the most effective way to master programming. Today, we will walk through the code-cleaning process and discuss the best techniques for transforming a messy program into a clean, functional one. Read through this article and uncover valuable insights.
Whether it’s in neural network systems, artificial intelligence, or other related software disciplines, debugging is essential. I believe that the most valuable skill you can develop is the ability to solve problems as they arise, and this skill becomes an integral part of you for future challenges of a similar nature. Thus, problem-solving can build a strong skill set, gradually transforming someone into an expert.
Collaborative Debugging
When I committed to writing this article, I was working on a project in which I encountered several errors while trying to compile the code. At times, the debugger would present me with 50 error lines to address. Through trial and error, I developed a routine for tackling bugs that allows me to resolve issues in just a few minutes, if not seconds, and get the program running smoothly.
Author: Clemence Benjamin