Quote - ... Given all that, it seems like we're going to be stuck with debugging via print statements just like I was doing back in the 80s.

Thank you for investigating all that for us, ElZagna. That truly is too bad... sprinkling print statements into your code doesn't hardly help at all: the output window fails to indicate whether a statement executed or not, or if not, why not. When I ran into snags in VBA, I'd step through stuff with watches on given valiables and generally be able to see where I introduced a bug or whatever.

With this environment, you pretty much have to be a PhilC or a Bagginsbill and write clean, error-free coded from the get-go. Forget about trying to sort out any mess you might have made: can't tell you how many times I've ended up with truncated mc6s because matmatic choked on some particularly bad segment of my code and output gave me a page of tracebacks which told me absolutely nothing about the problem.

At least with straight procedures (functions only), i could sort-of get to the bottom of things, but recently I've been trying to work with classes, and debugging is hopeless. :blink:

Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2

Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand] 

Metaphor of Chooks