You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Inserting print statements does not take much thinking at all, if not sure add a print statement to every branch of the code in question, then remove them one by one as you home in on the 'bug'. I do this often... It is much easier than deciding were to put break points in a debugger, and much faster than single stepping every line. Trust me :)
It looks crude, but when I'm at a loss where to put a print statement I often (temporarily) have...
Run it, then tidy up afterwards....
Run it, then tidy up afterwards....
No need to tidy up, just turn them off . . .
My way . . . https://www.mql5.com/en/forum/135598
No need to tidy up, just turn them off . . .
My way . . . https://www.mql5.com/en/forum/135598
Yup I have conditional logging too, just when extremely puzzled I put in a lot of extra temp logging which IMO clutters the readability of the code, so once I've fixed the bug, I remove it and just leave the more useful generic logging behind.
Yup I have conditional logging too, just when extremely puzzled I put in a lot of extra temp logging which clutters the readability of the code, so I remove it and just leave the more useful generic logging behind once I've fixed the bug.
I can live very happily without OOP
Me too. I think Richard Mansfield put it best when he said "OOP is to writing a program, what going through airport security is to flying"