Why are we not deleting namespaces of plugins when they are unloaded ?
Karel.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
Because if they have after scripts pending that would cause huge bugs...
And we can't clean after scripts :s
Phil
Karel Demeyer a écrit :
Why are we not deleting namespaces of plugins when they are unloaded ?
Karel.
can't we say that cleaning those after's is a task for the plugin maintainer
to do in the de-init procedure ? If something bugs then, it's the plugin's
fault, not aMSN ? For me it's weird that after unloading a plugin it's
still polluting memory ... Also this would make it really easy to see if a
I don't think we could force it, but it should be considered good
practice for a plugin to remove it's own namespace..
On 5 Jan 2008, at 16:00, Karel Demeyer wrote:
can't we say that cleaning those after's is a task for the plugin
maintainer to do in the de-init procedure ? If something
I agree, it's a good idea to delete the namespace. Problem is that some plugins
can have multiple namespaces (can, although I don't think any does).
So for that specific reason, I think that the plugin should do it by itself.
Maybe we could write a 'amsn-plugins-lint' that checks plugin's code
Hi,
As some of you may have noticed, we just had 34 commits today into SVN. That's
a lot.. and the cause ? the bug report system..
We just deleted all those old bugs that were already fixed or rare or whatever.
This made the bugs database shrink from 3 GB of bug reports to 28MB of
bug
