Quote:
Originally Posted by KevinH
And they can, just by including it. Also there is nothing keeping a plugin from importing code from another co-located plugin.
|
Absolutely.
...although I don't consider it wise to depend on the code (via importing) of co-located plugins that aren't under the direct control of the same developer. The other plugin could change and your plugin then becomes dead in the water.
Quote:
Originally Posted by varlog
I only mean if it were a "proper" library other plugins would be able to use it.
|
A wonderful idea. Great if it happens. It's just not practical to expect all plugin developers to adhere to the practice. Nor can the plugin infrastructure itself
force them to do so.
Why are we having this conversation again? The current plugin infrastructure provides enough flexibility to allow developers to be as generous, conscientious, and efficient as they want to be with their code.