Re: Optimizing Code Sense
Re: Optimizing Code Sense
- Subject: Re: Optimizing Code Sense
- From: "Mike Jackson" <email@hidden>
- Date: Sat, 1 Jul 2006 19:56:09 -0400
On 7/1/06, David Dunham <email@hidden> wrote:
On 1 Jul 2006, at 10:41, Mike Jackson wrote:
> What type of "#include" should I use? I currently put the full path to
> my files since I have the code in subdirectories?
I don't think this relates at all to CodeSense. But full paths sounds
like a bad idea, since you can't easily move code around. To specify
which folder a file's in, I've seen a fair amount of code use
something like
#include "sprite/AnimateSprite.h"
I did not really explain that very well. I really meant something like
you have instead of some absolute path. I should have been more
precise in my explanation.
Where as some of the other code that I inherited just has
#include "foo.h" where foo.h resides in some subdir. Then I have to
make sure in the build settings that the subdir is on the include
path.
which is actually cross-platform.
As for CodeSense, it seems to work worse with C++ (compared to
Objective-C), and even worse with stuff like templates.
Well, I am stuck with C++ as I have to have my code compile on a
number of platforms. Templates.. well I am still too new to C++ to
worry about them.. but their time will come..
David Dunham A Sharp, LLC
Voice/Fax: 206 783 7404 http://a-sharp.com
"People seem to misinterpret complexity as sophistication" -- Niklaus
--
Mike Jackson
imikejackson _at_ gee-mail 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