• 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: Cross-project references (was Re: Xcode's Find in Project)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cross-project references (was Re: Xcode's Find in Project)


  • Subject: Re: Cross-project references (was Re: Xcode's Find in Project)
  • From: Rua Haszard Morris <email@hidden>
  • Date: Tue, 20 Feb 2007 11:34:37 +1300

Hear hear.

Also the part about seeing Chris' point.

On Feb 20, 2007, at 11:25 AM, Paul Walmsley wrote:


Understood. I'm just trying to point out /why/ Xcode behaves the way it does. Xcode's project model is different than CodeWarrior's, and understanding how and why it differs will ultimately save you time and frustration when working with Xcode projects. It certainly doesn't mean that there's no room for improvement in Xcode's project model.
I can see your point -- it does highlight though the massive limitation of Xcode in terms of the way it deals with multiple projects. In large legacy applications (our codebase is around 1m LOC) it is impractical to organise projects other than with a number of library sub-projects (though in Xcode's model they may be peers, they are nonetheless part of a single 'uberproject'). Having to deal with anything that crosses the boundary between one library and another is painful -- it invariably involves having to manually open the other project file and explicitly search there.
Actually, I meant "#imported or #included." If you #import (Objective-C) or #include (C, C++) a header that has the declaration for a symbol, Xcode should have that symbol declaration in its project index. Command-double-clicking that symbol in your source code should take you to its declaration.
In theory, and for simple cases I'm sure that's true. In our large multi-project environment it's rarely the case. Often the #include isn't direct -- it may be an include of an include of a precompiled header, a prefix header or similar.

I am not wanting to knock the smartness or capability of Apple's engineers. I do however wish that the Powers That Be -- who dictate the directions of the tools development teams -- would prioritise decent support for *basic* IDE features before poncing about with graphical timeline interfaces. Grep is about 30 years old but *still* Finding across Projects doesn't work decently...

Paul
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40adinstruments.com


This email sent to email@hidden

_______________________________________________ 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
References: 
 >What are your top desired improvements in Xcode ? (From: Rob Barris <email@hidden>)
 >Re: What are your top desired improvements in Xcode ? (From: "Oscar Stiffelman" <email@hidden>)
 >Re: What are your top desired improvements in Xcode ? (From: Laurence Harris <email@hidden>)
 >Re: What are your top desired improvements in Xcode ? (From: "Theodore H. Smith" <email@hidden>)
 >Re: Cross-project references (was Re: Xcode's Find in Project) (From: Paul Walmsley <email@hidden>)

  • Prev by Date: Re: Cross-project references (was Re: Xcode's Find in Project)
  • Next by Date: Re: source code libraries
  • Previous by thread: Re: Cross-project references (was Re: Xcode's Find in Project)
  • Next by thread: Re: Xcode's Find in Project
  • Index(es):
    • Date
    • Thread