On 1/24/06, Jim Crafton <jim.crafton@gmail.com> wrote:
What happened? Is it just because the tool is so stable?

it had a single maintainer who had some family problems that have prevented him from doing anything on ectags for years now. (you can read his mails on the subject in the archive.) a big project like GCC is just going to keep rolling on, but a single-maintainer project is screwed in such a circumstance.

i wonder which of ectags' languages are actually used. the C++ support is fairly good, the Java support was okay until Java 1.5 came out, but the Perl and Ruby support is laughable. i'd imagine that it hurts ectags that it's written in C and C is the most stable language it supports. so the people most able/willing to fix stuff are the people with least need to.

it's also a bummer that ectags -- more so than compilers, even -- has to deal with malformed source. that makes it hard to just use (say) Sun's Java parser for the same job. ectags' crufty ad-hoc parsers might not be ideal to work on, but their ability to blindly struggle on in the face of near-nonsense input is pretty useful.

Elliott Hughes, http://www.jessies.org/~enh/