> > Classes found by ctags have no signature (the one of the corrsponding > > **init** method) while the ones of my script have > > Curious about this one - how does it behave when there are multiple > corresponding `__init__` functions with a different signature? Will it pick > just one of them for calltip? I'm asking because we now have this code > > https://github.com/geany/geany/blob/8f35d3342df724145ee9a6873e4ed3a18446211d/src/editor.c#L1867 > > which can look up all `__init__` functions for a class and display a > multi-calltip (with arrows on the side to scroll among the found calltips) > containing all the constructors.
In Python, there is no point in having multiple `__init__` methods. While technically possible, it makes no sense because the latter method overrides the previous one. The script here would probably pick one of them, I don't know which one, it is decided by the `inspect` library. > One more thing - wouldn't it make sense to factor-out the tag writing code to > a separate file so it can be reused by other tag writing scripts? For > instance, there's also `create_php_tags.py` which I think could reuse this > code too. And maybe this tag-writing code could be configurable to either > output the ctags format or the tag manager format - I can imagine that having > the tagmanager format could be useful for debugging. What do you think? Sure we can do that. But IMO both ideas would be better handled in seperate PRs to not blow this one even more. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3039#issuecomment-1315811428 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/3039/c1315811...@github.com>
