[Github-comments] [geany/geany] Ctags sync, part 1 (#1160)

Jiří Techet notifications at xxxxx
Thu Aug 4 07:39:13 UTC 2016


> I forgot to ask, why do we have dead code?

Because ctags isn't made to be a library - it's just a binary and we misuse it and use it in a library-like way. The result is that we use only some functions from some files while the rest is uninteresting for us.

In the future if I have time for this I'd like to add some real library support to uctags and there could be some ifdefs removing the dead code. But determining what is a dead code and what isn't is quite a lot of work and I don't want to do it in parallel with reducing the amount of changes between uctags and Geany.

> And why not do the whitespace changes file by file as you merge the ctags and Geany versions?

Because you cannot do the merge file by file but rather something like diff group by diff group spanning multiple files. If file A uses stuff from file B and if I merge only file A independently, the result won't compile because of the missing change in B. And the dependencies are much worse than just A->B, it's more like A->B, A->C, A->D, B->A, D->A.

But the main purpose of this patch set is to get parsers exactly to this state where they can be merged file by file so everyone can grab his favorite language and merge it independently of the rest and shouldn't be affected by any additional changes in the "main" part of ctags.

---
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/1160#issuecomment-237476778
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20160804/41fc1154/attachment.html>


More information about the Github-comments mailing list