Thread: [cedet-semantic] Finding the definition of a symbol
Brought to you by:
zappo
From: <jm...@bo...> - 2007-09-17 13:15:31
|
Hi, I'm just investigating CEDET for use in a big (about 30000 files) mixed C and C++ program (and lisp, but I've not yet done anything about that part). I'd like to be able to jump to the definition of a symbol in the C and C++ part. The autocompletion on field's names works (very slowly), so I think the database's setup is correct (even if it is not optiminal, I'll tune later if I decide to continue with CEDET), but I'm able to jump only to definitions in the current file (not even in files in the current directory). I probably have missed the obvious, but I fear I'll now continue to miss it until somebody shows it to me. Yours, -- Jean-Marc |
From: Eric M. L. <er...@si...> - 2007-09-17 15:06:20
|
HI, There are two jump routines bound to keys in senator. one is C-c , j which is just in one file, and the other is C-c , J which will jump across your project with a fancy completion thing to resolve many tags with the same name. There is also a function `semantic-ia-fast-jump' which tries to derive the full symbol under point and go there, but it doesn't ask questions, it just jumps. I know some people use Semantic for some stuff, but still use ETAGS or Cparse for jumping to symbols. There are different advantages to each, and they do not conflict. Eric >>> jm...@bo... seems to think that: >Hi, > >I'm just investigating CEDET for use in a big (about 30000 files) mixed C and >C++ program (and lisp, but I've not yet done anything about that part). > >I'd like to be able to jump to the definition of a symbol in the C and C++ >part. The autocompletion on field's names works (very slowly), so I think the >database's setup is correct (even if it is not optiminal, I'll tune later if I >decide to continue with CEDET), but I'm able to jump only to definitions in the >current file (not even in files in the current directory). I probably have >missed the obvious, but I fear I'll now continue to miss it until somebody >shows it to me. > >Yours, > -- Eric Ludlam: za...@gn..., er...@si... Home: http://www.ludlam.net Siege: www.siege-engine.com Emacs: http://cedet.sourceforge.net GNU: www.gnu.org |
From: <jm...@bo...> - 2007-09-17 16:37:26
|
Quoting "Eric M. Ludlam" <er...@si...>: > There are two jump routines bound to keys in senator. one is > C-c , j which is just in one file, and the other is C-c , J which will > jump across your project with a fancy completion thing to resolve many > tags with the same name. Ah here is my problem: the documentation gives all key bindings in upper case (so there is two C-C , J instead of a C-C , j and a C-C , J) and I didn't try with an uppercase J. While I'm sure I had tried with M-X semantic-complete-jump, it is possible that I did that only when my setup was not correct. > I know some people use Semantic for some stuff, but still use ETAGS > or Cparse for jumping to symbols. There are different advantages to > each, and they do not conflict. Either I'm messed up the configuration or ETAGS find too often things which are not definitions. cscope crashes on my code base. And C-Parse homepage makes it look superseded by cedet; I'll try it if the above doesn't works well for me. Thanks -- Jean-Marc |
From: Eric M. L. <er...@si...> - 2007-09-17 18:46:11
|
>>> jm...@bo... seems to think that: >Quoting "Eric M. Ludlam" <er...@si...>: > >> There are two jump routines bound to keys in senator. one is >> C-c , j which is just in one file, and the other is C-c , J which will >> jump across your project with a fancy completion thing to resolve many >> tags with the same name. > >Ah here is my problem: the documentation gives all key bindings in upper case >(so there is two C-C , J instead of a C-C , j and a C-C , J) and I didn't try >with an uppercase J. While I'm sure I had tried with M-X >semantic-complete-jump, it is possible that I did that only when my setup was >not correct. Uh, what documentation is that? It should be fixed. >> I know some people use Semantic for some stuff, but still use ETAGS >> or Cparse for jumping to symbols. There are different advantages to >> each, and they do not conflict. > >Either I'm messed up the configuration or ETAGS find too often things which are >not definitions. cscope crashes on my code base. And C-Parse homepage makes >it look superseded by cedet; I'll try it if the above doesn't works well for >me. Sorry, I meant cscope. My fingers still type cparse apparently. cparse is much slower than the new semantic stuff which does supersede it. There are some other tools that do this stuff also. Check out emacswiki.org for more. Eric -- Eric Ludlam: za...@gn..., er...@si... Home: http://www.ludlam.net Siege: www.siege-engine.com Emacs: http://cedet.sourceforge.net GNU: www.gnu.org |
From: <jm...@bo...> - 2007-09-18 07:18:03
|
Quoting "Eric M. Ludlam" <er...@si...>: > >>> jm...@bo... seems to think that: > >Quoting "Eric M. Ludlam" <er...@si...>: > > > >> There are two jump routines bound to keys in senator. one is > >> C-c , j which is just in one file, and the other is C-c , J which will > >> jump across your project with a fancy completion thing to resolve many > >> tags with the same name. > > > >Ah here is my problem: the documentation gives all key bindings in upper > case > >(so there is two C-C , J instead of a C-C , j and a C-C , J) and I didn't > try > >with an uppercase J. While I'm sure I had tried with M-X > >semantic-complete-jump, it is possible that I did that only when my setup > was > >not correct. > > Uh, what documentation is that? It should be fixed. The dvi file made from user-guide.texi (using texinfo 4.9). The contents of the texi file looks correct, and the info file made from it shows also the lower-case j. Looks like a problem in texinfo. Yours, -- |
From: <ls...@lo...> - 2007-09-19 14:43:45
|
Hi, Is there also a way to jump to the declaration of the symbol only? Most of the time I am only interested in how the function/methode is declared and what comments are around the declaration? Thanks! Nathan Eric M. Ludlam schrieb: >>>> jm...@bo... seems to think that: >>>> >> Quoting "Eric M. Ludlam" <er...@si...>: >> >> >>> There are two jump routines bound to keys in senator. one is >>> C-c , j which is just in one file, and the other is C-c , J which will >>> jump across your project with a fancy completion thing to resolve many >>> tags with the same name. >>> >> Ah here is my problem: the documentation gives all key bindings in upper case >> (so there is two C-C , J instead of a C-C , j and a C-C , J) and I didn't try >> with an uppercase J. While I'm sure I had tried with M-X >> semantic-complete-jump, it is possible that I did that only when my setup was >> not correct. >> > > Uh, what documentation is that? It should be fixed. > > >>> I know some people use Semantic for some stuff, but still use ETAGS >>> or Cparse for jumping to symbols. There are different advantages to >>> each, and they do not conflict. >>> >> Either I'm messed up the configuration or ETAGS find too often things which are >> not definitions. cscope crashes on my code base. And C-Parse homepage makes >> it look superseded by cedet; I'll try it if the above doesn't works well for >> me. >> > > Sorry, I meant cscope. My fingers still type cparse apparently. > cparse is much slower than the new semantic stuff which does > supersede it. > > There are some other tools that do this stuff also. Check out > emacswiki.org for more. > > Eric > > |
From: Eric M. L. <er...@si...> - 2007-09-23 16:11:29
|
Hmmm. I expend energy trying to throw away the prototypes to find the implementation in many situations. Fortunately, everything is available with the jump routine I showed below. Using C-c , J will let your jump to anything that matches a symbol name. If you press TAB when a symbol is "complete" or ambiguous, it will show you where you would land for each symbol of the same name. Sadly, it is not as convenient as just pressing RET when it shows you the nice default, but it ought to do what you want. Eric >>> =?ISO-8859-1?Q?Nathan_H=FCsken?= <ls...@lo...> seems to think that: >Hi, > >Is there also a way to jump to the declaration of the symbol only? >Most of the time I am only interested in how the function/methode is >declared and what comments are around the declaration? > >Thanks! >Nathan > >Eric M. Ludlam schrieb: >>>>> jm...@bo... seems to think that: >>>>> >>> Quoting "Eric M. Ludlam" <er...@si...>: >>> >>> >>>> There are two jump routines bound to keys in senator. one is >>>> C-c , j which is just in one file, and the other is C-c , J which will >>>> jump across your project with a fancy completion thing to resolve many >>>> tags with the same name. >>>> >>> Ah here is my problem: the documentation gives all key bindings in upper case >>> (so there is two C-C , J instead of a C-C , j and a C-C , J) and I didn't try >>> with an uppercase J. While I'm sure I had tried with M-X >>> semantic-complete-jump, it is possible that I did that only when my setup was >>> not correct. >>> >> >> Uh, what documentation is that? It should be fixed. >> >> >>>> I know some people use Semantic for some stuff, but still use ETAGS >>>> or Cparse for jumping to symbols. There are different advantages to >>>> each, and they do not conflict. >>>> >>> Either I'm messed up the configuration or ETAGS find too often things which are >>> not definitions. cscope crashes on my code base. And C-Parse homepage makes >>> it look superseded by cedet; I'll try it if the above doesn't works well for >>> me. >>> >> >> Sorry, I meant cscope. My fingers still type cparse apparently. >> cparse is much slower than the new semantic stuff which does >> supersede it. >> >> There are some other tools that do this stuff also. Check out >> emacswiki.org for more. >> >> Eric >> >> > > >------------------------------------------------------------------------- >This SF.net email is sponsored by: Microsoft >Defy all challenges. Microsoft(R) Visual Studio 2005. >http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >_______________________________________________ >cedet-semantic mailing list >ced...@li... >https://lists.sourceforge.net/lists/listinfo/cedet-semantic > |