Scratch

Thanks for the support. String variables for the input boxes would be automatically created but for other things yea, good idea. It should be an option.

[Make new variable]
     [Type:               ]
     [Number Variable]
     [String Variable   ]

I thought about whether I would like booleans or not.  Frankly, I like the old "c" solution best---any numeric variable can be used where a Boolean expression is wanted, with 0 meaning false and non-zero meaning true.  This avoids the need to create a new type, and allows having ordinary variables set to 1 and 0 as booleans.  It annoys me a little that scratch insists on using   x > 0 in tests, rather than just x.  (Particularly for variables like "treasure found" I would like to have tests like "wait until treasure found".)

For boolean variables, the "=true" test is redundant.  In languages that have booleans, using ==true and ==false is generally a sign of a beginning programmer, who doesn't understand how to use booleans.

When one does not have booleans, one can use ordinary variables with =0  and >0, but that is not quite as elegant.