Well...
The trouble is that a plugin can't remove its own namespace in a clean
way...
In the other hand, if the plugin is buggy and doesn't remove its after
script we will have plenty users who will yield about bugs in aMSN and
that mean must things to do for us : it means that we will have to w
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 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 bu
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
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.
>
>
>
> -
