No, because essentially we’re just accessing the plugin object (passing nothing to it) and then calling the function on that object. The problem, to a certain degree, is about namespacing the plugin, so what if we just create a “sub-plugin” like as follows:

$.fn.plugin_func = function() {}
and call it with $(‘#foo’).plugin_func();

Basically it is just another plugin, but by name (only) related to the main plugin. You could still access the main plugin objects etc. from the “sub-plugin”. For example getting the defaults = $.fn.plugin.defaults.

I’ve not done a plugin that works like I’m describing and so I have no idea of the problems involved in working across plugins. If you do try it out, please let me know how you get on. Good luck!

The “var” there is not required, as options is already a local variable by virtue of being an argument.