• 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: Optimizing Code Sense
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Optimizing Code Sense


  • Subject: Re: Optimizing Code Sense
  • From: David Dunham <email@hidden>
  • Date: Sat, 1 Jul 2006 14:48:51 -0700

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.

David Dunham A Sharp, LLC
Voice/Fax: 206 783 7404 http://a-sharp.com
"People seem to misinterpret complexity as sophistication" -- Niklaus Wirth



_______________________________________________ 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: Optimizing Code Sense
      • From: "Mike Jackson" <email@hidden>
References: 
 >Optimizing Code Sense (From: "Mike Jackson" <email@hidden>)

  • Prev by Date: Re: Supporting Multiple SDK's Without Warnings
  • Next by Date: Re: CVS and resource files
  • Previous by thread: Optimizing Code Sense
  • Next by thread: Re: Optimizing Code Sense
  • Index(es):
    • Date
    • Thread