But it's not a retroactive change. It's only for new projects. It
won't break anything or introduce anything different than not having
the macros but kind-of sort-of implying that they're there by having
predefined DEBUG/RELEASE build configurations. I have a hard time
understanding how predefining DEBUG/NDEBUG in new project templates
in the obvious way would break projects in unexpected ways. I think
that 90% of developers would like this and the rest wouldn't care.
It clearly wouldn't break existing PROJECTS, but a number of times
I've gotten open source projects, and found the easiest way to set up
dependencies and make Universal builds was to dump them into an Xcode
project. I don't *think* they would have broken by having additional
#ifdefs, but you never know.
David Dunham
Voice/Fax: 206 783 7404 http://www.pensee.com/dunham/
Imagination is more important than knowledge. -- Albert Einstein
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
