Most of the plugins now complain about GeanyFunctions being deprecated which makes the compilation output rather noisy. I have removed GeanyFunctions from my plugins but this requires bumping API to a post-linkage-cleanup build, which is 224.
To get rid of the warnings there are two options:
1. Remove geany_functions and bump the API requirement for every plugin. 2. Guard the geany_functions declaration with a macro checking the API version.
I'd personally vote for (1) otherwise the deprecated declaration gets never removed. Is it a problem to bump the API requirement? Is it common to build new plugin versions with old Geany versions?
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/382
I'd also agree for (1).
I've just done this for the Addons and SpellCheck plugins.
Keeping compability with old Geany versions is a nice-to-have I'd say but not really necessary as we try to release Geany-Plugins together with Geany itself. So this should be fine.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/382#issuecomment-192827729
Agreed, we should rather drop them. And as it's already in 1.26 even.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/382#issuecomment-192922820
Good, will prepare a patch.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/382#issuecomment-192937516
Closed #382 via #388.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/382#event-582118862
github-comments@lists.geany.org