[Asterisk-Dev] Module unloading

[Rich Adamson]

> I still don't see how this is a sollution which can be used by module 
> developers in short term... This is the whole point of the problem... 
> ofcourse it can be fixed in the core... but that doesn't help anyone at 
> this point, it will also need good testing, some icky stuff will happen. 
> However it's a good thing that it will be fixed in the future...
> 
> Other than that you are pushing this into a discussion between atexit() 
> or unload_module()... which it isn't... I am pointing out that the 
> "documentation" is incorrect regarding the current implementation. Which 
> is *very* annoying for module developers. All I wanted to do is raise 
> some attention on this subject so that we could see if it could be fixed 
> in the long term... and propose a short term sollution to module 
> developers (which already exists in existing * installations, in 
> contrary to your sollution).

I'm not a developer, but this list/system is highly oriented around
placing your thoughts/code in the bug tracker even if its relatively
simple text changes. If the text is reasonable, someone will move it
into cvs sooner or later. So, open a bug and others can add comments
to it.