@kugel- commented on this pull request.
- to the members ending with @c _perform are called by Geany at appropriate
+ * moments to inform the plugin when to perform the given feature. + * + * The extension is defined by the pointers in the PluginExtension structure and + * is registered in Geany using the @c plugin_extension_register() function. + * + * @warning The API provided by this file is subject to change and should not be + * considered stable at this point. That said, it is highly probable that if + * a change of this API is required in the future, it will not be of a major + * nature and should not require major modifications of the affected plugins + * (e.g. added/modified parameter of a function and similar changes). + **/ +typedef struct +{ + /** + * Pointer to function called by Geany to check whether the plugin
Perhaps confusing for you, but to me it's clear: This is a table of callbacks implemented by the plugin. It's obvious to me that the plugin can chose any name internally.
For reference, see `GeanyProxyFuncs` that we already have documented
```
/** Hooks that need to be implemented by every proxy * * @see geany_plugin_register_proxy() for a full description of the proxy mechanism. * * @since 1.26 (API 226) **/ struct GeanyProxyFuncs { /** Called to determine whether the proxy is truly responsible for the requested plugin. * A NULL pointer assumes the probe() function would always return @ref GEANY_PROXY_MATCH */ gint (*probe) (GeanyPlugin *proxy, const gchar *filename, gpointer pdata); /** Called after probe(), to perform the actual job of loading the plugin */ gpointer (*load) (GeanyPlugin *proxy, GeanyPlugin *subplugin, const gchar *filename, gpointer pdata); /** Called when the user initiates unloading of a plugin, e.g. on Geany exit */ void (*unload) (GeanyPlugin *proxy, GeanyPlugin *subplugin, gpointer load_data, gpointer pdata); }; ```
Anyway I don't request a change here, just that it's worded strangely to my programmer eyes.