It's not only SuperBasic that is nearly beyond me but programming in general. I looked at a Boggle algorithm in Python. I could not follow it, even though it was short. Looking at the code I got the impression that it contained some powerful "Objects" that did most of the work. This kind of assistance is not available to the SBasic programmer.TMD2003 posted:-
Some people out there still think SuperBASIC is beyond them.
As I have posted on a number of occasions, I try and program for fun (weird, I know). I have an SBasic programming environment derived from the original SMS2 setup (SMS2 did not contain an interpreter). I use this to learn how to program and thought I would have a go at writing a very basic but playable Boggle program.
It's playable in the sense that one can use the cursor keys to select shuffled characters to make words that are then stored in a string and then displayed in a daughter job. The program should really be written using QPTR but I am only just beginning to understand it, so it's a fixed window program with flashing cursor control.
It's currently 45 lines of code, plus 8 lines for the daughter job. There's no dictionary and I only shuffle each dice in a fixed location.
There's no symbol for a "Qu" so I add a "U" if "Q" is selected. There is quite a nice shuffle animation.
It is certainly a "crap game". It was designed to run on SMSQE at 1024x768 (or more) its in B&W so that it can run on my Q68 setup. I don't use any special instructions (apart from WAIT) , it could be "shrunk" to fit QL resolutions and so I see no reason why it could not be classed as a "crap" QL program.
The WAIT instruction is an SMS2 instruction but I am sure there is a SuperBasic equivalent.