Masatake YAMATO

I'm not sure I understand what you want. As a principle of u-ctags design, ctags works only for valid input. If you pass -DFINAL=final -DOVERRIDE=override, ctags sees: ``` PUBLIC off_t...

> As I explained before, my exemple works with OVERRIDE and ctags shows the override property. So why final is not ? This looks bug. As you wrote: > BUT,...

> Give me time. I will show my idea. Adding `final` to the `properties:` field is not a good idea as I wrote. If you want to attach `final` to...

``` @1 _intervaltab { dup :kind /function eq { ``` `@1` represents the start position of the 1st group of the regex pattern. `_intervaltab` is for an operator accessing the...

I call it optscript mostly derived from postscript. See https://ctags.io/2021/01/05/optscript/ . It is not documented yet and is immature. While sketching the idea, I found two critical bugs. One is...

You are interested in ``` ctags --_list-operators ```

I remembered I wrote about optscript a bit: https://docs.ctags.io/en/latest/optscript.html

It looks hard to fix.

While working on https://github.com/bootlin/elixir/issues/379, I found a way to solve this issue. ``` $ cat -n input.c 1 SYSCALL_DEFINE3(faccessat, int, dfd, const char __user *, filename, int, mode) 2 {...

The result implies that ftell(), a standard C function, returns -1. ftell returns -1 when an error occurs. ftell() is called indirectly from setTagFilePosition(). When I developed the code, I...