🚀 go-pugleaf

[]

When debugging AL programs I sometimes generate a bad CHK on purpose
at a point in the program that should not be reached.  The six bombs
stand out on the screen...  Another trick is to use -1 (rather than
0) as the "invalid" pointer-offset value in variables.  Then if
you use an uninitialized such variable you get a tell-tale 3-bombs.

Note though that sometimes you'll get 2 or 3 crashes together, and the
number of bombs on the screen when the smoke clears will be the sum
of the numbers output by each crash.  SO if you get, say, 8 bombs
it _could_ really be 3+3+2.

A good debugger beats all of the above...

- Moshe Braner