As you can see, the 8th call was [mis-]typed as "Explode The To" [sic].
Of course, he meant "Explode the Top".
I assumed that CSDS would blow up on the sequence -- however, it let it go through, which surprised me.
Something was obviously wrong. So I started playing with it, and it turns out that instead of doing an "Explode the Top", the program just performed an "Explode". Seems to be a bizarre parsing bug, perhaps matching the substring (all but the last "p" character) to the extent of treating the string as permissible input, but then not resolving to the correct node. (?)
It would be fine if the program offered a warning/error message, but simply performing a different call than was entered is really easy to miss if you aren't keeping an eagle eye on the formation diagrams.
Not a likely/common error to happen, but it is an embarrasment "waiting to happen" for a caller eventually...
