Let me rephrase. We want to have one way of referencing a build
setting in the future (in both build settings and scripts) to
reduce confusion, what form that takes is a secondary issue that
is not decided at this point. Obviously, choosing a more more
familiar form for the referencing is preferable (as long as the
chosen form doesn't imply behavior that is false or non-existent).
Well, since $() means something entirely different in shell
scripts, I think ${} would be the most logical.
My vote for this, too. Having different brackets depending on wether
Xcode or bash reads the variable would be really confusing.
On the other hand, I don't think it would hurt to leave $() valid
in build settings (for backward compatibility reasons).
Even better: Since there is no change in functionality, Xcode could
automatically "upgrade" to the new convention. Makes a nice
application for text field validation ...
_______________________________________________
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
