Re: Xcode - An Apple Embarrassment NOT
Re: Xcode - An Apple Embarrassment NOT
- Subject: Re: Xcode - An Apple Embarrassment NOT
- From: Joar Wingfors <email@hidden>
- Date: Mon, 05 Mar 2012 22:54:38 -0800
On 5 mar 2012, at 15:05, Brian Lambert wrote:
> "XCode 4 does not index files in blue folders"
>
> Does this mean that if I create my own folder hierarchy on disk, placing my various .h/.m files into different folders to organize my code files on disk, that Xcode 4 won't index my code?
It's typically easy to verify if your files are being indexed or not - Check the Symbol Navigator. Generally speaking, Xcode is optimized for dealing with files that are being included by targets in your projects. As always, if Xcode doesn't support something that you think it should support, please file a bug report.
> If so, could someone tell me what will stop working?
A lot of functionality in Xcode depends on having information about the symbolic contents of your projects (syntax coloring, code completion, navigation, etc.). Some of this functionality is derived from directly parsing a file as it is being opened in the editor (this gives you information about that file, and other files that it in turn includes), some of it is derived from information in the index (this gives you information about other files being included by targets in your projects). The functionality that can be provided by parsing the file as it is being opened would typically work regardless of if there is additional information to be found in the index.
If your project is set up in a way that prevents Xcode from being able to successfully index all of your sources, then your user experience will be degraded. For example: You can't "Jump to Definition" from file Foo to a method definition in file Bar unless Bar has been successfully indexed. Why? Because the information about methods being defined in Bar would have to come from the index, and could not be found by parsing Foo.
> Could this explain why Issue Navigator is no longer taking me to the source line of code for issues?
Not sure, but I wouldn't think so. If Xcode has found an issue in your project, it should per definition have enough information to take you to that issue. If you can reproduce a problem of that nature, please file a bug report.
Joar
_______________________________________________
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