Re: Optimizing Code Sense
Re: Optimizing Code Sense
- Subject: Re: Optimizing Code Sense
- From: "Mike Jackson" <email@hidden>
- Date: Sat, 1 Jul 2006 19:57:48 -0400
On 7/1/06, Michael Rice <email@hidden> wrote:
> On Jul 1, 2006, at 4:48 PM, David Dunham 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"
>>
>> 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.
And CodeSense simply loses its mind when it comes to C++ namespaces.
Oh how I wish Apple would devote some time to fixing these flaws.
OK.. so no namespaces.. that might be problematic.. but I could manage...
I am almost positive someone at Apple is devoting time to this....
--
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