>>>>> "DP" == Dejan Pangercic writes:
DP> a)is there a way to jump to the function/class definition from where
DP> the function/class is used in the code stack? I thought
DP> "semantic-analyze-proto-impl-toggle" would do a job, but I get "Could
DP> not find suitable prototype" message back.
M-x semantic-symref function do this job
DP> b)Where does CEDET store its tags after preprocessing the source code?
DP> I cannot find them nowhere in CEDET installation nor in my project's
DP> c)As evident from my config file, I am using "ede-cpp-root-project"
DP> for specifying the code to be pre-processed and I also learnt that it
DP> is settable. Now, could I also somehow use the variable I set
DP> "ede-cpp-root-project" to, to navigate me directly to the project root
DP> for instance? I found it very convenient in Kdevelop for instance
DP> where you could just fire it up, open the project and get all the
DP> files associated with this project brought to you. Is there anything
DP> like that possible with CEDET at all?
You can take look on the ECB project (http://ecb.sf.net), latest versions
of it take defined ede-projects into account, and allows to show
directories & files, that are belonging to selected projects
With best wishes, Alex Ott, MBA