As long as time is only used as a local variable the name clash doesn't really matter. I don't think it's likely we will ever use time() within the simulation itself. And in any case the clash becomes apparent as soon as one tries to call time as a function and can then easily be fixed.
I've changed divorce according to your suggestion. Generally, though, it would be nice to have a uniform, simple mechanism to make global information available to the simulation functions. Having an ad hoc API for every function (e.g. the additional houses and towns arguments in this case) is a bit annoying. If there is no easy way to do that in MultiABM, we can keep adding wrapper functions like in this case, but it would be nicer to just have every function take a model argument and be done with it.
As long as time is only used as a local variable the name clash doesn't really matter. I don't think it's likely we will ever use
time()within the simulation itself. And in any case the clash becomes apparent as soon as one tries to call time as a function and can then easily be fixed.I've changed divorce according to your suggestion. Generally, though, it would be nice to have a uniform, simple mechanism to make global information available to the simulation functions. Having an ad hoc API for every function (e.g. the additional houses and towns arguments in this case) is a bit annoying. If there is no easy way to do that in MultiABM, we can keep adding wrapper functions like in this case, but it would be nicer to just have every function take a model argument and be done with it.