I'm very surprised that @b4n has rewritten two parsers of u-ctags.
Improving Cobol and Flex parsers are welcome but... @b4n, what will you do if someone adds more regex basedd parsers to u-ctags. Replacing the regex engine of u-ctags is more effortless.

Adding support for u-ctags regex parser would be better and is the goal, but it's not easy, and certainly not effortless -- see @techee's work 🙂
The reason why I worked on the parsers is that we'd need something working in the next release for COBOL and ActionScript, relase which is supposed to happen next weekend, which is awful close, and I didn't expect getting the regex parsers to work would be a trivial task that would take a couple of hours and be robust. So I figured that it was safer to work on 2 parsers, as if there really was a problem with them it would only affect users of those, not potentially everyone. And well, while at it I figured I could probably improve parsing for the relevant languages given those regex parsers seemed quite basic.
Also to be fair you failed to take into account my tendency to write parsers for languages I don't know 😀

I'll answer the rest later, hopefully today.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.