A bit of history on this. The original reason extensions are unloadable in the first place is that in the NetLogo GUI, we don't want loaded extensions to accumulate in memory as you open a series of models that use a variety of extensions.
So the unload method exists to support that; it allows an extension to release resources so that its classloader can be garbage collected. When NetLogo is about to quit anyway, that doesn't matter, so we don't bother to call unload. That said, it's perfectly logical that you wanted to use `unload` for some other purpose -- to release other kinds of resources for other reasons. So asking `unload` to be called under additional circumstances seems to me like a reasonable request. (You could lodge it at https://github.com/NetLogo/NetLogo/issues.) I'm just giving the history to show that the current behavior isn't bizarre or merely a bug. -- Seth Tisue | Northwestern University | http://tisue.net developer, NetLogo: http://ccl.northwestern.edu/netlogo/ -- 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.
