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
interesting xcode behaviour
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
interesting xcode behaviour
Subject
:
interesting xcode behaviour
From: Markian Hlynka <
email@hidden
>
Date: Fri, 18 Jun 2004 15:54:37 -0600
I have discovered some interesting xcode behaviour, and I'm not sure if it's a feature or a bug.
I have several targets in a project. Most of them share a common main(), and most of their code, with only a few files different.
Recently, I added a complete, self-contained file to the project. (its own main and symbols and everything) Just to be explicit, the new file is exactly that. a single file with lots of functions! :) (I didn't do it!)
Anyway, I have some variables declared in interface.cc in my regular targets:
interface.cc:
Move_T PV;
in ab.cc, I have
extern Move_T PV;
Previously, if I command-clicked on an instance of the PV variable in ab.cc, it would take me to the declaration in interface.cc.
Since I've added the new file, it takes me instead to an identically named variable in the new file! remember, there are no includes, or ANY shared functions or data across these two SEPARATE targets. I didn't write the code in the new file, so I can't avoid the fact that we use some similar (global!) variable names.
Is this supposed to happen? It's as if all global variables share a common indexing, despite belonging to different targets. And it seems that the most recent addition takes precedence.
I suppose I should add that I'm using the most recent public releases of everything (xcode, OS X, etc) and that all my targets still build and execute properly. Thus, it seems to be an IDE thing, not a compiler thing.
Thoughts?
Markian
PS: I got several complements on my "great looking IDE" from some linux geeks yesterday (well, geeks in training). Way to go, Apple! Now, if some of the functionality could get a little more tweaked... :) (I know you're working on it; this isn't disparagement, it's a complement!
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
Follow-Ups
:
Re: interesting xcode behaviour
From:
Scott Tooker <email@hidden>
Prev by Date:
Best way to copy files into package
Next by Date:
Re: Best way to copy files into package
Previous by thread:
Re: Best way to copy files into package
Next by thread:
Re: interesting xcode behaviour
Index(es):
Date
Thread