> What do you want to achieve with the flags alone? You still need params to > say to *which* name/scope/lang/type/whatever to filter for.
It was more a general comment on API design, since you mentioned about making functions extensible. Like if you wanted to add more boolean options or different types of attributes to filter by, etc, you can add those in without breaking the API/ABI. > This interface isn't just a workaround for my python problem. You said you made it because you couldn't accomplish what you wanted in Python efficiently enough. That's where you usually would write a Python extension module to work around the inefficiencies. > It's a new interface for both Geany and plugins because the existing methods > to query tags are poor (inflexible and inconsistent), such that I wouldn't > want to even export in the first place.For plugins there isn't any method > provided by Geany ATM, just the global workspace (with bare tag arrays) is > exported. I'm not too keen on exporting any TM stuff FWIW. I'd like to see TM/Ctags as some kind of fallback tag handling that can be disabled by plugins who provide better filetype-specific support in the future. At least the one nice thing about the current TM for plugins is that it's a nice thin API that allows plugins to still accomplish whatever they want (KISS). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/1187#issuecomment-242416504
