[Geany-Devel] Plugin API design question/change proposal

2014-05-20 Thread Matthew Brush
Hi, Does anyone know why the plugin API was designed to use a bunch of structures containing function pointers, hidden behind macros in geanyfunctions.h? I found the commit where this stuff was added initially (ie. plugin ABI 2-3) but it doesn't mention why it was done like this and I tried

Re: [Geany-Devel] Plugin API design question/change proposal

2014-05-20 Thread Lex Trotman
On 20 May 2014 19:29, Matthew Brush mbr...@codebrainz.ca wrote: Hi, Does anyone know why the plugin API was designed to use a bunch of structures containing function pointers, hidden behind macros in geanyfunctions.h? I found the commit where this stuff was added initially (ie. plugin ABI

Re: [Geany-Devel] Plugin API design question/change proposal

2014-05-20 Thread Matthew Brush
On 14-05-20 03:38 AM, Lex Trotman wrote: [snip] I know it might be a bit hard to restrict some symbols, like enums that C spits gaily into the global namespace, but if functions and structs are limited to those intended to be available, then that will be a big leap forward. It should be ok if