Overloaded use of 'Build Configuration' in Swift and Xcode is confusing

Originator:dempsey
Number:rdar://19812930 Date Originated:2/12/15
Status:Open Resolved:
Product:Developer Tools Product Version:
Classification:UI/Usability Reproducible:Always
 
The phrase ‘Build Configuration’ is used both in Xcode and Swift to mean different things - both related to building/compiling code, but different things.

It is confusing to overload terminology in this way, since an Xcode build configuration is not a Swift build configuration, but you could set the flag for a Swift build configuration in an Xcode build configuration.

(Re-read that last paragraph. It would read a lot better if ‘build configuration’ wasn’t the same term for both).

Please consider calling it something like a ‘build conditions’, ‘build options’, ‘build predicates’ or something similar in Swift.

(So many documents, articles, tutorials, etc. have been written about Xcode build configurations since they were introduced in 2005, changing the term in Xcode would lose a great deal of knowledge.)

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!