It has many problems and should not be used in production code if at all possible.
Things like EvalString( Concatenation( "QUIMP_", String(deg) ) ) can probably be replaced by ValueGlobal( Concatenation( "QUIMP_", String(deg) ) ). Even better would be to instead use the language feature that is meant for this, and instead use a big array/list indexed by the degree -- as I understand it, it'll have at most 4095 entries, so its size should be no problem. (Though if it was, one can also index records by integers, and use them as a kind of "spare array" this way)
It has many problems and should not be used in production code if at all possible.
Things like
EvalString( Concatenation( "QUIMP_", String(deg) ) )can probably be replaced byValueGlobal( Concatenation( "QUIMP_", String(deg) ) ). Even better would be to instead use the language feature that is meant for this, and instead use a big array/list indexed by the degree -- as I understand it, it'll have at most 4095 entries, so its size should be no problem. (Though if it was, one can also index records by integers, and use them as a kind of "spare array" this way)