Will typedefs confuse semantic/cedet?  Our code uses a lot of typedefs, and if semantic does not understand them, it will be a significant problem.

I was editing one buffer, and saw that the TAGS, C++, Project, Senator and SRecoder menus were all empty.  I ran semantic-analyze-debug-assit at a function that I wanted to find references for, and saw the output below.  The code near the point was

  Paths solve( const GlwDigraph::Node& rGlwUniversalNode,
               double& rSolutionCost );

and the point was in solve.  (This is a header file.)  It has recognized Paths as a typedef, but seems unable to use that.

Is this expected behavior?

Troy



Unable to find datatype for: "class Paths solve (const class GlwDigraph::Node rGlwUniversalNode,double rSolutionCost)".
Declared type is: "class Paths {}"
Raw data type is: ("Paths" type (:type "class") nil nil)

Semantic could not find this data type in any of its global tables.

Semantic locates datatypes through either the local scope, or the global
typecache.

Local Scope Information:
 * Tag Class Constraint against SCOPE: (type)
 >> Known parent types with possible in scope symbols:
  "namespace glw {}"
  class StitchingGraphNSAlg {}

 >> Known symbols within the current scope:
  typedef OrigArcFlowBoundMap {}
  typedef ArcCostMap {}
  typedef OrigArcCostMap {}
  typedef SplitDigraph {}
  typedef NetworkSimplexType {}
  typedef Paths {}
  class Path {}
  typedef NodeSupplyMap {}
  typedef NodeTreeMap {}
  typedef ArcFlowMap {}
  typedef ArcTreeMap {}
  typedef OrigDigraph {}
  typedef GlwArcFlowBoundMap {}
  typedef FlowBound {}
  typedef Cost {}
  typedef GlwArcCostMap {}
  typedef GlwDigraph {}
  class StitchingGraphNSAlg {}

 * No known symbols declared locally.
Semantic creates and maintains a type cache for each buffer.
If the type is a global type, then it should appear in they typecache.
To examine the typecache, type:

  M-x semanticdb-typecache-dump RET   [ Do It ]

Current typecache Statistics:
      1 types global in this file
    136 types from includes.

If the datatype is not in the typecache, then your include
path may be incorrect.  

Include Path Summary:

This file's project include search is handled by the EDE object:
  Buffer Target:  #<ede-cpp-root-target /home/troy/insight/views/fusion-graphtracking-insight-ft2-STO202-branch/src/graphBuildingCore/graphSolvers/>
  Buffer Project: #<ede-cpp-root-project insight-sto202>
  Backup Locator: #<ede-locate-base Loc>


The system include path is:
  /usr/include
  /usr/local/include/
  /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.5.3/include/
  /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.5.3/include-fixed/
  /usr/include/
  /usr/local/include/c++/4.5.3/
  /usr/local/include/c++/4.5.3/x86_64-unknown-linux-gnu/
  /usr/local/include/c++/4.5.3/backward/


Include Summary: /proj/insight/staff/troy/views/fusion-graphtracking-insight-ft2-STO202-branch/src/graphBuildingCore/graphSolvers/StitchingGraphNSAlg_decl.h

StitchingGraphNSAlg_decl.h contains 8 includes.
   Unknown Includes:  0
   Unparsed Includes: 0
   Parsed Includes:   8

 No unknown includes.

[back]