Tinderbox v9 Icon

Store interim code values in variables or attributes

Historically, this was done by storing data in attributes. That works but if, for instance, this involves storing lots of really large lists, it is easy for unneeded stored data to accumulate unless the attribute values are reset.

Better is to use variables unless there is a genuine need to persistently store such data. Very occasionally, and less encountered today, it may prove necessary to 'crystallise' a calculated value before using it in another expression. Typed variables generally remove that older requirement.

Variables have he advantage of clearing themselves up. They are created when needed during a a complex action, where there may be all sorts of different interim values being created. At the end pf the code running the variables are destroyed.

To record a variable's value for review after running the code, logging is the best approach.