Optimizing Code Sense
Optimizing Code Sense
- Subject: Optimizing Code Sense
- From: "Mike Jackson" <email@hidden>
- Date: Sat, 1 Jul 2006 13:41:18 -0400
There have been several threads on this list about the code sense
indexing and how it isn't maybe living up to what some of us were
expecting. Rather than curse at it for not working I understand that
there are limitations, or situations in which the indexer does not
handle well.
My question is simple and is aimed at the Apple guys/gals to answer.
What are some things that I can do when I am writing my code that will
"help" the indexer find everything? I am still a bit wet behind the
ears with C++, but I also have the luxury of changing some of my code
around so that the Xcode experience can be the best that it can be.
What type of "#include" should I use? I currently put the full path to
my files since I have the code in subdirectories?
How about #defines?
How about namespaces? File structure within my source tree?
Classes? Inheritance?
Thanks for any suggestions. Keep up the good work. See you at WWDC....
--------
Mike Jackson
imikejackson <at> gmail <dot> com
_______________________________________________
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