|
|
| kmcintyre Veteran   Posts: 132 Joined: 9/12/2007 Location: Valley Center, CA  User Profile | I am attaching a version of indDebug that appears to be working reliably based on 2 years of indicator readings on 1 stock. I ABSOLUTELY consider this a bug in OL. The bug was not in my logic, but with the compilers incorrect parsing of the syntax. And it cost me a week. More over, it has completely eroded my confidence in any code I write in OL. Lesson learned, do not trust OL. I must spend hours verifying the execution of any code segment, regardless of how straight forward the logic appears to be. Further, the code I just spent a week on is a VERY small part of the #system I coded. Apparently I will need to unit test every logical construct within the #system to have any confidence in the combined result. I had 3 decades of experience coding everything from machine code entered directly into a DataIO PROM programmer, to assembly, to basic, pascal, c, c++. c#. Java, and many other languages on Unix, Windows, DOS, Apple, iRMX, and many other realtime operating environments. I designed and built satcom systems, turbine and reciprocating engine control systems,, medical devices, many shrink wrap software products, and multi-tier eCom business systems. I ended my career as CTO of a Fortune 500 systems integration firm. I qualify as an EXPERT witness. And in my PROFFESSIONAL opinion... THis is a bug. Further, OT is one of the most unstable and bug ridden platforms I have ever attempted to developed code on. Of course you are entitled to your opinions. And I am entitled to my frustrations... Thanks for finding a workaround... Peace, Out  Attached file : indDeug.txt (1KB - 851 downloads) |
