Early this year I was asked by Ian Cox and Brady Brady to put together a small group of individuals to create a general document discussing good programming practices when developing routines, large or small, using JSL. This document would address a problem many of you have heard, “The latest version of JMP breaks my JSL programs”. If you are new, or have not encountered this issue, see here or here for recent examples. We were asked that the document be made short, descriptive rather than prescriptive. Our goal (Mike Anderson, Mark Bailey, Ian, and myself) was to create a foundation for what would likely be created afterwards (the how-to part).
Our goal was to create something that could be understood by any technical staff member, regardless of their JSL programming experience. Please read over the document and plan to discuss any questions you have, particularly if something doesn’t make sense or you feel something is missing. If you have any questions or comments, please post them below or bring them to the meeting. While implementation details are outside of the scope of this document, it would be helpful to know what you think should be addressed first.
Thanks, Don
24 July - I added the slides from today's Midyear meeting.
@DonMcCormack has posted the document in the SE Knowledge Base: Good Programming Practices.
I'm turning off replies here. Please add your comments to that document.
Great thoughts here!
At the risk of introducing some scope creep, this doc could be a great guide to leave users with at the start of their JSL crafting i.e. after a scripting demo or JMP Day. It would be nice to see key resources called out (Scripting Index and Guide, Log, Community File Exchange, etc.) to turn the doc into a ‘1 stop shop’ reference for such beginning scripters. Such additional content would have to be balanced to maintain brevity and avoid any ‘TL;DR’ situations, though...
