Compiler created errors..
Compiler created errors..
- Subject: Compiler created errors..
- From: Stephen Northcott <email@hidden>
- Date: Tue, 20 Jan 2009 15:10:14 +0700
Is there a project size, or set of housekeeping rules that needs to be
applied to large XCode projects?
i.e. Does it need some TLC once you hit so many hundred files with so
many thousand lines...
In the last 48 hours I have had two very very hard to find bugs, that
I have traced to the point of knowing the problem but it actually not
being their in the source..
One was a value getting corrupted randomly from a totally unrelated
class.
A Watch on that variable trapped it, but only a Clean all would clear
the "bug".
In the second instant two similarly named functions were getting
swapped about by the compiler.
Again a Clean all as a last resort cleared the "bug".
At the back of my mind a little gnome keeps telling me to do a Clean
all, and re-compile..
I have resisted this because I really don't expect a compiler to make
errors compiling your source.
You know, it's like the old adage.. If you know 100% there is a driver
bug then it's 100% likely it's actually a bug in your code!
In both instances, as a last resort, a Clean all has resolved the bug,
proving (to me anyway) that XCode / gcc was corrupting it's
intermediate build files...
Does anyone else get this?
Is there a generally accepted project size / cache requirement, or
something I might not be aware of.
Or is this just one of those things?
Thanks for any feedback.
Stephen.
_______________________________________________
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