On Fri, 23 May 2008 21:16:33 +0300 Yura Siamashka yurand2@gmail.com wrote:
On Fri, 23 May 2008 12:49:18 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Maybe we could drop almost all the pre-0.14 deprecated stuff. The more recent deprecated macros I added to make porting easier. But we should be clear why if we do this - e.g. do the macros cause name conflicts for plugin authors often?
I encounter name conflicts few times, it is rare enought to be annoying. But why keep useless garbage since:
- Every old plugin just have to be modified to compile with new API
anyway.
It makes it easier to make plugins compatible with Geany 0.15, less replacements needed.
- Do you know plugins that still use them?
It depends which macros you're talking about, but I assume the old function pointer struct macros. Not off hand, but until last week at least one was using them.
One reason why I haven't dropped the old function macros yet is because sometime I can imagine having an auto-generated wrapper library for the geany_functions function pointers, so plugins can just write the function name like in the core. Not sure how difficult it would be to auto-generate yet.
How these macroses will help with auto-genearating? If some script generate code it should not matter what to generate.
They don't. But plugin authors might have to switch from documents-> to p_document-> to document_. Keeping the original macros might mean only one switch. But probably it's not much work to port anyway.
Regards, Nick