So the command line cannot be used while debugging a script.
- The script editor of ACL 10 is very useful. It was about time to get line numbering and color coding for the code, and it is a great help for any ACL™ programmers out there.
- Having the additional “Variable” navigator on the left hand side is very useful as well: In combination with the debugger, it makes script development a lot easier.
- For debugging, you can go step-by-step through your scripts, and/or set break points within the code.
- ACL Indicates where it stopped if an error occurred.
- Two thing that I personally miss, but this is probably the “Tecci” in me:
- Currently it is not possible to use the command line when debugging a script. I understand the reasons (you could mess around too much, delete all variables etc.), but I kind of missed it anyway – but this may only be me. :-)
- As second point I would have loved was to be able to debug within a group. Very often this is the tricky part when coding: To control your variable content when performing a group.
But I do not complain, in fact I am happy about the new functionality. All in all it is a big improvement, and if you want to write ACL™ scripts, and you do not have it yet, you should definitely consider updating to ACL™ AN 10.5 to get these features.
I hope you enjoyed this little walkthrough! For any comments on that article, feel free to write us at firstname.lastname@example.org
To contact the author you can also use LinkedIn or XING (you may have to login first before you can access these links).