The default initialization of non-interface globals to 0 gets in the way at times. Could changing this to `null` be considered? Similarly, clearing non-interface globals should reset them to `null`.
Example: consider a model with many global variables (too many to conveniently add interface widgets for all). Sometimes it is nice to create BS experiments that set some of these globals. Now in `setup-globals`, we want to set the default values of all our non-interface global variables, but only if a value has not been set by BS. The obvious (?) approach is testing for 0, but is a problem, because the experiment may involve setting a 0 value. Being able to test against `null` would resolve this problem (and have other advantages). Thanks for considering, Alan Isaac -- You received this message because you are subscribed to the Google Groups "netlogo-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
