A global variable defined by the globals keyword that is never set to a value has the value 0 by default. This seems reasonable.
However, if the global variable was set in a previous run of the same model (i.e. since the model was loaded), but is not set in the current run, the variable inherits the value from the previous run. To me this seems unreasonable. It's the kind of thing that could introduce a bug that's difficult to track down. But maybe there's a use-case for which this behavior was intended? -- 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 netlogo-devel+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
