First Spear Posted August 24, 2015 Share Posted August 24, 2015 Hey all. I killed a bunch of productivity time for myself recently by forgetting to put appropriate guard statements in places in an IntyBASIC program. I am now considering making a little Win32 program "iblint" to scan my .bas file and make recommendations where problems might exist, for example no WAIT between MODE and PRINT, or no MUSIC REPEAT/STOP at the end of a song sequence, et . Please share your comments on what rules should be followed, could be followed, etc. I have not thought this all the way through, but if I port some table-driven rule logic from work, it would be easy to turn checks on/off as IntyBASIC (or a coder) matures. *don't code tired. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.