Home » Language IDEs » C / C++ IDE (CDT) » ctags & cscope
| ctags & cscope [message #85771] |
Fri, 14 November 2003 19:29  |
Eclipse User |
|
|
|
Originally posted by: spamreceptor.yahoo.com
Hi,
A friend that writes Java pointed me to eclipse as a good editor. I write
C. I am fairly allergic to VI. Thus CDT looks like a great alternative.
However, VI guys have ctags and cscope. For those that don't know, ctags
generates a table of all the definitions of all symbols in the project.
Want to know where the source for a function name is or what a macro is
defined as? Point VI at your "tags" file and poof you are there. Cscope
is even more powerful in that it builds a table of every refernce of every
symbol. Want to know all the locations where a function is called? VI
will show you a list with a little context and you simply navigate there.
This is real important for working with 3rd party or legacy software.
Note this is far far faster than searching all files in the project for a
symbol each time since the table is already generated.
My understanding is that the java eclipse editor has equivalent things
build in, and that CDT does not. Is this true? And if so, is there any
hope for change? My VI using friend is laughing at me as we speak. He
uses ctags and just added cscope and is now editing far faster than me.
It would be unfortunate to cave and have to use VI in insert mode because
I refuse to learn the cryptic key sequences...
While I understand such tools as Visual Slick Edit and Source Insight have
such features, they are also $300.00 and that's $300 more than VI. I
think they are only available for the Windows platform.
Thank you in advance for your help.
|
|
|
| Re: ctags & cscope [message #85786 is a reply to message #85771] |
Sat, 15 November 2003 05:10  |
| Eclipse User |
|
|
|
Well, CDT had ctags before CDT1.2. They took that of in favour of the
new Parser/Indexer thing, but this one is not fully implemented yet, as
I would say. Most functionality is right now available by the C/C++
Search feature.
My feelings right now are, its not sufficient yet, cause:
* you have to bring up the search dialog first,
* searching takes a while (don't know what takes that long)
* not everything is found (no context information for current cursor
position)
For the first point, couldn't there be a input view for search view,
which is opened like the other views, and one can switch fast over by
keystroke to this input view?
The Content Assist feature needs to be up as fast as possible. Someone
at Redhat made some searching/conversion from different documentation
sources, I wonder why this doesn't get to the community, though one
could take a look on this and help on working and bugfixing. Maybe the
guys from Redhat will change their opinion (thinking about
SourceNavigator, is this one still maintained?).
What I miss right now are Refactoring features, but they will come.
Unfortunately, it will be to late for my work I do right now.
I think, CDT-team does a good job, and I'm sure CDT itself is not their
main project. Though, it's like me, I'm involved in the CDT as I
encounter bugs or find ways for enhancements, but my main project comes
first and this keeps me from digging deeper into CDT development.
Pat Kuhl wrote:
> Hi,
>
> A friend that writes Java pointed me to eclipse as a good editor. I write
> C. I am fairly allergic to VI. Thus CDT looks like a great alternative.
> However, VI guys have ctags and cscope. For those that don't know, ctags
> generates a table of all the definitions of all symbols in the project.
> Want to know where the source for a function name is or what a macro is
> defined as? Point VI at your "tags" file and poof you are there. Cscope
> is even more powerful in that it builds a table of every refernce of every
> symbol. Want to know all the locations where a function is called? VI
> will show you a list with a little context and you simply navigate there.
> This is real important for working with 3rd party or legacy software.
> Note this is far far faster than searching all files in the project for a
> symbol each time since the table is already generated.
>
> My understanding is that the java eclipse editor has equivalent things
> build in, and that CDT does not. Is this true? And if so, is there any
> hope for change? My VI using friend is laughing at me as we speak. He
> uses ctags and just added cscope and is now editing far faster than me.
> It would be unfortunate to cave and have to use VI in insert mode because
> I refuse to learn the cryptic key sequences...
>
> While I understand such tools as Visual Slick Edit and Source Insight have
> such features, they are also $300.00 and that's $300 more than VI. I
> think they are only available for the Windows platform.
>
> Thank you in advance for your help.
>
>
>
|
|
|
| Re: ctags & cscope [message #85800 is a reply to message #85786] |
Sat, 15 November 2003 16:18 |
| Eclipse User |
|
|
|
Originally posted by: spamreceptor.yahoo.com
I'm not aware of what other parsing they do other than the search feature.
The main reason the search tool is unacceptable is because of speed. It
simply takes way too long compared to anyone using cscope. Cscope is far
faster since it only opens one file and has to index only once. The
second problem is that it does not remember past searches in any useful
way so you take that huge search time hit everytime.
In my opinion, ctag support should be put back because it is stable and
useful already. Then cscope should be integrated for the same reason.
Searching files will only be useful for very small projects. Whatever
search algorithm that is currently used by CDT, is far slower than what
Ultraedit does. Granted, Ultraedit is not free. But is is the cheapest
commercial editor I've seen and is almost complete. It is missing cscope
support and its diff tool is not integrated.
I understand I am being quite critical of a free product, but I believe
these criticisms to be constructive.
kesselhaus wrote:
> Well, CDT had ctags before CDT1.2. They took that of in favour of the
> new Parser/Indexer thing, but this one is not fully implemented yet, as
> I would say. Most functionality is right now available by the C/C++
> Search feature.
> My feelings right now are, its not sufficient yet, cause:
> * you have to bring up the search dialog first,
> * searching takes a while (don't know what takes that long)
> * not everything is found (no context information for current cursor
> position)
> For the first point, couldn't there be a input view for search view,
> which is opened like the other views, and one can switch fast over by
> keystroke to this input view?
> The Content Assist feature needs to be up as fast as possible. Someone
> at Redhat made some searching/conversion from different documentation
> sources, I wonder why this doesn't get to the community, though one
> could take a look on this and help on working and bugfixing. Maybe the
> guys from Redhat will change their opinion (thinking about
> SourceNavigator, is this one still maintained?).
> What I miss right now are Refactoring features, but they will come.
> Unfortunately, it will be to late for my work I do right now.
> I think, CDT-team does a good job, and I'm sure CDT itself is not their
> main project. Though, it's like me, I'm involved in the CDT as I
> encounter bugs or find ways for enhancements, but my main project comes
> first and this keeps me from digging deeper into CDT development.
|
|
| | |
| Re: ctags & cscope [message #85845 is a reply to message #85815] |
Mon, 17 November 2003 08:48 |
| Eclipse User |
|
|
|
Tom Tromey schrieb:
>>>>>>">" == kesselhaus <kesselhaus@gmx.net> writes:
>
>
>>>The Content Assist feature needs to be up as fast as possible. Someone
>>>at Redhat made some searching/conversion from different documentation
>>>sources, I wonder why this doesn't get to the community, though one
>>>could take a look on this and help on working and bugfixing. Maybe the
>>>guys from Redhat will change their opinion (thinking about
>>>SourceNavigator, is this one still maintained?).
>
>
> We're planning on contributing the content assist patch. I don't know
> the timeline, but it definitely will happen. Currently we've got
> converters to convert help for Gtk, X11, and glibc into the property
> files that the content assist patch uses.
Thats sounds great, but the thing with the timeline is what gives your
plugin announcement some mysthic touch. ;)
As Content Assist feature is asked for on this list quite often, people like
me can just say, "There is something in planning/progress, but I dont
know for sure."
I'm looking for such thing too btw., and I could think about contributing
some "hacks" or provide some docs maybe, or I would test it, But I would
not like to write one right now for timing reasons of my own projects.
> Source Navigator is no longer maintained by Red Hat, but I believe
> there is a SourceForge fork of it. This doesn't seem directly
> relevant to the CDT though.
>
> Tom
Well, I just remember SourceNavigator as I had been using it a while ago but
did not see much change today.
I don't want to say Redhat, what it has to do, I just meant that someone
would maybe contribute if Redhat could release something to test.
Anyway, I'm still looking forward to test your Content Assist and see it
grow.
|
|
|
| Re: ctags & cscope [message #85916 is a reply to message #85845] |
Tue, 18 November 2003 00:26 |
| Eclipse User |
|
|
|
Originally posted by: spamreceptor.yahoo.com
Either you guys are hijacking my thread, or I don't know what Content
Assist is... or both :D
Nor do I know what Source Navigator is. Could someone explain? Thanks.
Henning Riedel wrote:
> Tom Tromey schrieb:
> >>>>>>">" == kesselhaus <kesselhaus@gmx.net> writes:
> >
> >
> >>>The Content Assist feature needs to be up as fast as possible. Someone
> >>>at Redhat made some searching/conversion from different documentation
> >>>sources, I wonder why this doesn't get to the community, though one
> >>>could take a look on this and help on working and bugfixing. Maybe the
> >>>guys from Redhat will change their opinion (thinking about
> >>>SourceNavigator, is this one still maintained?).
> >
> >
> > We're planning on contributing the content assist patch. I don't know
> > the timeline, but it definitely will happen. Currently we've got
> > converters to convert help for Gtk, X11, and glibc into the property
> > files that the content assist patch uses.
> Thats sounds great, but the thing with the timeline is what gives your
> plugin announcement some mysthic touch. ;)
> As Content Assist feature is asked for on this list quite often, people like
> me can just say, "There is something in planning/progress, but I dont
> know for sure."
> I'm looking for such thing too btw., and I could think about contributing
> some "hacks" or provide some docs maybe, or I would test it, But I would
> not like to write one right now for timing reasons of my own projects.
> > Source Navigator is no longer maintained by Red Hat, but I believe
> > there is a SourceForge fork of it. This doesn't seem directly
> > relevant to the CDT though.
> >
> > Tom
> Well, I just remember SourceNavigator as I had been using it a while ago but
> did not see much change today.
> I don't want to say Redhat, what it has to do, I just meant that someone
> would maybe contribute if Redhat could release something to test.
> Anyway, I'm still looking forward to test your Content Assist and see it
> grow.
|
|
|
| Re: ctags & cscope [message #85944 is a reply to message #85916] |
Tue, 18 November 2003 05:25 |
| Eclipse User |
|
|
|
Pat Kuhl schrieb:
> Either you guys are hijacking my thread, or I don't know what Content
> Assist is... or both :D
Content Assist is the something like "IntelliSense" in Visual Studio.
When you hover over the code you get information about the thing
underneath your cursor. Also things like "AutoComplete" could be
part of this.
> Nor do I know what Source Navigator is. Could someone explain? Thanks.
Take a look at http://sourcenav.sourceforge.com and see the online docs.
They also have some screenshots in the docs describing the features.
SourceNavigator actually incorporates ctags and cscope into a TCL/TK GUI.
Some of the features of this I would like to see in Eclipse CDT too.
> Henning Riedel wrote:
>
>
>>Tom Tromey schrieb:
>>
>>>>>>>>">" == kesselhaus <kesselhaus@gmx.net> writes:
>>>
>>>
>>>>>The Content Assist feature needs to be up as fast as possible. Someone
>>>>>at Redhat made some searching/conversion from different documentation
>>>>>sources, I wonder why this doesn't get to the community, though one
>>>>>could take a look on this and help on working and bugfixing. Maybe the
>>>>>guys from Redhat will change their opinion (thinking about
>>>>>SourceNavigator, is this one still maintained?).
>>>
>>>
>>>We're planning on contributing the content assist patch. I don't know
>>>the timeline, but it definitely will happen. Currently we've got
>>>converters to convert help for Gtk, X11, and glibc into the property
>>>files that the content assist patch uses.
>
>
>>Thats sounds great, but the thing with the timeline is what gives your
>>plugin announcement some mysthic touch. ;)
>>As Content Assist feature is asked for on this list quite often, people like
>>me can just say, "There is something in planning/progress, but I dont
>>know for sure."
>>I'm looking for such thing too btw., and I could think about contributing
>>some "hacks" or provide some docs maybe, or I would test it, But I would
>>not like to write one right now for timing reasons of my own projects.
>
>
>>>Source Navigator is no longer maintained by Red Hat, but I believe
>>>there is a SourceForge fork of it. This doesn't seem directly
>>>relevant to the CDT though.
>>>
>>>Tom
>
>
>>Well, I just remember SourceNavigator as I had been using it a while ago but
>>did not see much change today.
>
>
>>I don't want to say Redhat, what it has to do, I just meant that someone
>>would maybe contribute if Redhat could release something to test.
>
>
>>Anyway, I'm still looking forward to test your Content Assist and see it
>>grow.
>
>
>
|
|
| | |
| Re: ctags & cscope [message #90761 is a reply to message #85771] |
Mon, 29 December 2003 12:04 |
| Eclipse User |
|
|
|
Originally posted by: spamreceptor.yahoo.com
I'm bumping this question to see if anything has changed. Has the indexer
been added to CDT yet? By this I mean something other than a brute force,
search-all-files one at a time.
Thanks.
Pat Kuhl wrote:
> Hi,
> A friend that writes Java pointed me to eclipse as a good editor. I write
> C. I am fairly allergic to VI. Thus CDT looks like a great alternative.
> However, VI guys have ctags and cscope. For those that don't know, ctags
> generates a table of all the definitions of all symbols in the project.
> Want to know where the source for a function name is or what a macro is
> defined as? Point VI at your "tags" file and poof you are there. Cscope
> is even more powerful in that it builds a table of every refernce of every
> symbol. Want to know all the locations where a function is called? VI
> will show you a list with a little context and you simply navigate there.
> This is real important for working with 3rd party or legacy software.
> Note this is far far faster than searching all files in the project for a
> symbol each time since the table is already generated.
> My understanding is that the java eclipse editor has equivalent things
> build in, and that CDT does not. Is this true? And if so, is there any
> hope for change? My VI using friend is laughing at me as we speak. He
> uses ctags and just added cscope and is now editing far faster than me.
> It would be unfortunate to cave and have to use VI in insert mode because
> I refuse to learn the cryptic key sequences...
> While I understand such tools as Visual Slick Edit and Source Insight have
> such features, they are also $300.00 and that's $300 more than VI. I
> think they are only available for the Windows platform.
> Thank you in advance for your help.
|
|
|
Goto Forum:
Current Time: Fri May 09 08:25:50 EDT 2025
Powered by FUDForum. Page generated in 0.10275 seconds |
Home