Originally Posted By: johnnyp
Can Zorro not be a little more specific as to the cause of the error?

Could Zorro not provide a call trace? Just knowing which line of code called the function that crashed would be nice. Knowing the function call hierarchy up to the most recent run() or tick() call would be even better.


Imo if you want better code and debugging then you should consider DLL strategies. See http://www.zorro-trader.com/manual/en/dlls.htm

Zorro comes bundled with the DLL API. It's easier to use than Lite-C.

For a better c++ API you can clone https://github.com/xezon/zorro-dll (was made for ZorroBeta_1.70.7 as proof of concept).

Feedback on above implementation would be much appreciated.