Hi All, I have this brainstorm which I'd like to get some feedback on.
I reckon it's a bad idea to make source browsing info with a separate program like cscope or etags. I reckon it's the compiler's job. Why? (1) Because only the compiler can do it authoritatively, after all, it decides what's in your executable. (2) Doing it properly involves following #ifdefs and #includes, which the compiler already does. (3) Because the types of tag you want are defined by the language. (4) Because there's very little to it after parsing, which the compiler is already doing. I imagine doing it for c++ and outputting cscope format which is reasonably expressive and popular. I have no idea how hard it would be, but if I can bug people for help I'd be willing to give it a shot. Is there any interest in something like that? Adrian. PS: I'm not talking about local text completion here. I"m talking about finding your way around a huge project where cscope etc give 50 different definitions of any important function because they can't follow the #ifdefs.
