> Give me some time to look over the Exuberant Ctags code-base and I'll > see what I can do. > Can there be some general discussion with, exactly what are the > shortcomings of the current parser: > > * Is there a problem with ctags not understanding that entity > blocks and architecture blocks are connected in a fundamental > way? > * Are there library functions and constructs that are just too > much for the current implementation? What do those look like? > * Is ctags recognition outdated? > * Is it ctags job to recognize things like flipflops, muxers or > non-synthesizable constructs?
From the discussion, Exuberant Ctags is using regexp to generate tags. This works, but not very well (for example if you add a newline or a comment). The advantage of generating Ctags from ghdl is that this is accurate and up to date. Note that the Ctags technology is somewhat old and poor. We can do much better to handle hiding, overload and cross-file references. That's a larger project... > I know the topic was on a project of larger scope but, for an IDE > ctags is an important part of what people expect from one. > Without good parsing support, the market for the up-and-coming IDE > will be blasé at best. With this and that I work a full time job in > mind, > don't expect sudden results; If there is a wanting for new features I > will do my best. Sure! Tristan. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
