CEDET

Default searches for symbols optimizes in C/C++ by looking in headers.
To get a broader search, thus finding the implementations, it is
important for an app like eassist to use an analyzer to do that extra
work.

semantic-ia-fast-jump has some of this logic in it where it analyzes
your code to differentiate between prototypes and implementation.

Eric

On Wed, 2009-10-28 at 14:41 -0700, Suvayu Ali wrote:
> Hi everyone,
> 
> I am working with a C++ framework called ROOT[1]. eassist-list-methods 
> seems to fail to recognize the implementation for methods of a class 
> which is automatically generated by the framework from a data tree. The 
> auto-generated code gets written in a strange way, maybe that is the reason.
> 
> The include is like this,
> >  // myclass.h
> >  #ifndef myclass_h
> >  #define myclass_h
> >
> >  class
> >  {
> >  ...
> >  virtual return_type method1(...);
> >  virtual return_type method2(...);
> >  ...
> >  }
> >
> >  #endif
> >
> >  #ifdef myclass_cxx
> >
> >  return_type myclass::method1(...)
> >  {
> >  ...
> >  }
> >
> >  #endif // #ifdef myclass_cxx
> 
> and some more methods are defined in another file called myclass.C like
> this,
> >  // myclass.C
> >  #define myclass_cxx
> >  #include myclass.h
> >
> >  return_type myclass::method2(...)
> >  {
> >  ...
> >  }
> 
> Every time I do M-m and select a method from the list, I end up in the 
> declaration of the method within class {...} rather than in the 
> implementation. Is their a way to make this work? This is not something 
> very important, if it works it would be just a little more convenient 
> that is all.
> 
> Thanks for any inputs.
> 
> [1] http://root.cern.ch

Hi,

Using semantic-ia-fast-jump also gives me the same result.

On Tuesday 03 November 2009 07:17 AM, Eric M. Ludlam wrote:
> Default searches for symbols optimizes in C/C++ by looking in headers.
> To get a broader search, thus finding the implementations, it is
> important for an app like eassist to use an analyzer to do that extra
> work.
>
> semantic-ia-fast-jump has some of this logic in it where it analyzes
> your code to differentiate between prototypes and implementation.
>
> Eric
>
> On Wed, 2009-10-28 at 14:41 -0700, Suvayu Ali wrote:
>> Hi everyone,
>>
>> I am working with a C++ framework called ROOT[1]. eassist-list-methods
>> seems to fail to recognize the implementation for methods of a class
>> which is automatically generated by the framework from a data tree. The
>> auto-generated code gets written in a strange way, maybe that is the reason.
>>
>> The include is like this,
>>>   // myclass.h
>>>   #ifndef myclass_h
>>>   #define myclass_h
>>>
>>>   class
>>>   {
>>>   ...
>>>   virtual return_type method1(...);
>>>   virtual return_type method2(...);
>>>   ...
>>>   }
>>>
>>>   #endif
>>>
>>>   #ifdef myclass_cxx
>>>
>>>   return_type myclass::method1(...)
>>>   {
>>>   ...
>>>   }
>>>
>>>   #endif // #ifdef myclass_cxx
>>
>> and some more methods are defined in another file called myclass.C like
>> this,
>>>   // myclass.C
>>>   #define myclass_cxx
>>>   #include myclass.h
>>>
>>>   return_type myclass::method2(...)
>>>   {
>>>   ...
>>>   }
>>
>> Every time I do M-m and select a method from the list, I end up in the
>> declaration of the method within class {...} rather than in the
>> implementation. Is their a way to make this work? This is not something
>> very important, if it works it would be just a little more convenient
>> that is all.
>>
>> Thanks for any inputs.
>>
>> [1] http://root.cern.ch
>


-- 
Suvayu

Open source is the future. It sets us free.