View Single Post
mystic_fm

 
Member Since: Mar 15, 2007
Posts: 161
mystic_fm will become famous soon enough
Mac Specs: 17" MacBook Pro, 2.33GHz C2D, 2GB RAM

mystic_fm is offline
Sorry, I won't visit the link you provided (particularly since MediaFire shows many reports of popups and browser exploits on SiteAdvisor).

In all of the smaller Xcode projects I've encountered, header files are usually dumped into both the same physical folder and the same "project group" as their corresponding implementation files (i.e., either "Classes" or "Other Sources", whichever is appropriate). However, there's nothing constraining you from categorizing things in the project differently if you wish. At a minimum, you could easily add a "Header Files" project group to "virtually" separate the header files if that would make things feel more familiar to you.

(Ignore the next two paragraphs if they are too confusing.)

You could go a step further and also create a separate physical location for those files. In this case, just remember that the compiler for each source file needs to be able to find the referenced header files, so if you have them physically separated, you must either specify a relative path to those header files in your #include (or #import) directives, or else add each of the header file folders to the "user header search path" in the project's build settings.

By the way, you could also organize your header files differently in Visual Studio if you wanted to ... the default project organization that VS gives you is not cast in stone either.
QUOTE Thanks