Re: Xcode 2.0 Questions and Wishlist
Re: Xcode 2.0 Questions and Wishlist
- Subject: Re: Xcode 2.0 Questions and Wishlist
- From: "Frederick C. Lee" <email@hidden>
- Date: Sat, 26 Mar 2005 09:15:21 -0800
Good Point: using XCode as a portal to the Open Source World.
I like it.
Ric.
On Mar 25, 2005, at 10:54 AM, Andreas Grosam wrote:
I do not have a pre-release version of XCode, so i would appreciate it
if we could discuss this here - if possible.
Firstly, i would much appreciate a better support for C++ templates
regarding debugging. This would require another debug format than the
current one used in the Apple compiler.
Then, i also would find it very helpful, if the indexer would be
improved from the ground up. In particular, i miss the capabilities of
proper parsing and reporting of namespaces, local classes and
templates at all. And i also wish much greater detail of information
- and some smarter location of the source files - means, taking care
of comments above or beneath identifiers.
Also a problem of the indexer is its lack of parsing all variants of
header files. For instance, the common C++ headers, e.g. <vector>
will not be parsed at all.
Furthermore, the indexer should create an index for each target - and
it should only display those symbols which actually belong - or are
defined - in the current active target. For instance, the macro NDEBUG
may be defined or not, or it may be even defined differently in
several places. The indexer should be able to track all its
definitions appropriately.
What about an index per translation unit? Sounds weird, but actually
this is what we need -and this is the only acccurate way to go!
Additionally, i would appreciate if symbols defined per built-in or
via command-line would be also listed.
Then, i would much appreciate some non-trivial example projects -
which an associated tutorial which explains each aspect in detail. For
example, projects which deal with frameworks, plug-ins, shared and
static libraries, in its various ways and which shows how they can be
composed together and eventually making a final product.
Well, this would certainly improve the (presently steep) learning
curve.
The header-map. You now what i mean - just bug-fixing.
I expect that a header map will function properly! This implies, that
we need a list of header locations for *each file*! Even the
translation unit is not sufficient - their might be ambiguities!
This is because the location of a header depends on the search paths
defined, the current existing paths while compiling and the location
of the file which is including this file.
This also requires that the header map must be checked for validity
before each compilation of a translation unit. For instance, they
become invalid, when the search paths changes, or when the system
header changes, when sources will be moved, or ..etc. etc.
Yeah, and XCode should become Open Source!
Thanks to all contributing to XCode.
I strongly believe, that it will become the tool we all wanted.
Regards
Andreas Grosam
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
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