• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Jump to Definition doesn't
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Jump to Definition doesn't


  • Subject: Re: Jump to Definition doesn't
  • From: Marc Epard <email@hidden>
  • Date: Fri, 02 Jun 2006 11:25:17 -0500
  • Thread-topic: Jump to Definition doesn't

on 6/1/06 5:32 PM, Chris Espinosa wrote:

> The litmus test  is to look in your "Project Symbols" smartgroup, sort it by
> name, and  see if symbols have multiple definitions, and if so, which ones are
> bogus.

Looking in Project Symbols was very enlightening.  First I noticed there
were very few of our header files (.hpp) represented there.  Then, by
filtering out only locations ending in .hpp I could see which headers were
being indexed and which were not.  This suggested some experiments which
revealed the problem.

Virtually all of the symbols in this code base are in nested C++ namespaces
and the file hierarchy matches the namespace nesting.  As a result almost
all of the includes look like this:

#include "Name/Space/SomeClass.hpp"

It's the partial path that causes the indexer to exclude symbols in this
header even though the compiler happily includes it.  If I add the
Name/Space/ directory to USER_HEADER_SEARCH_PATHS and change to #include
"SomeClass.hpp", SomeClass.hpp gets indexed.  If this is not a know issue,
let me know and I'll file a bug.

A work-around that seems viable is to Get Info on a header file (or files)
and change the type to sourcecode.cpp instead of sourcecode.cpp.h, then
selecting Include In Index.  I'm guessing this causes the files to be
indexed directly instead of by way of being included.  I'm not sure if this
has undesirable side-effects, though.

> A list of misinterpretations that you find would help us fix  those
> cases in the parser.

I suspect misinterpretations might not be a problem now that the definition
is there.  I'll let you know

-Marc

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Jump to Definition doesn't
      • From: Marc Epard <email@hidden>
References: 
 >Re: Jump to Definition doesn't (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: ADC Reference Library is not optimized for Mac OS X?
  • Next by Date: Re: Installing Xcode 2.3
  • Previous by thread: Re: Jump to Definition doesn't
  • Next by thread: Re: Jump to Definition doesn't
  • Index(es):
    • Date
    • Thread