<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 16, 2016, at 6:02 PM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 16, 2016, at 9:55 AM, David Waite <<a href="mailto:david@alkaline-solutions.com" class="">david@alkaline-solutions.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">(repost) </div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br class=""></div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Two comments:<div class=""><br class=""></div><div class="">- I’ll specifically call out that I think treating this as an alias rather than a new platform is appropriate - it would be confusing for users if the existing #if os(osx) did not match Sierra.</div><div class=""><br class=""></div><div class="">- Do you anticipate a separate proposal deprecating #if os(osx) ?</div><div class=""><br class=""></div><div class="">-DW</div></div></div></div></div></blockquote><div class=""><br class=""></div><div class=""><span style="font-family: Palatino-Roman;" class="">I do not anticipate deprecating the OSX test. Swift will and can be deployed to OS X as well as macOS. I've been tossing this around in my head for a few days now and my thoughts are:</span></div><div class=""><span style="font-family: Palatino-Roman;" class=""><br class=""></span></div><div class=""><span style="font-family: Palatino-Roman;" class="">* the configuration test should not remain as #if os(OSX) because that's the wrong name</span></div></div></div></div></blockquote><div><br class=""></div><div>Agreed.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><span style="font-family: Palatino-Roman;" class="">* replacing OSX with macOS places an undue burden on existing code</span></div></div></div></div></blockquote><div><br class=""></div><div>Since Swift 3.0 is a code-breaking change my guess is that there is no burden if the Xcode migration assistent automatically changes all #if os(osx) to #if os(macos), thus deprecating the term osx, not burdening the developer at all.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><span style="font-family: Palatino-Roman;" class="">* aliasing the two may cause issues down the road ("why does this test have two names") but I think developers are smart enough to figure out why both variations exist</span></div></div></div></div></blockquote><div><br class=""></div><div>I don't see them as two different OSs, mostly since version-wise it's OS X 10.11 and macOS 10.12. It's the same OS, different name - it IMHO should be an alias. </div><div><br class=""></div><div>If iOS was renamed to phoneOS and kept versioning, you'd still expect #if os(ios) to be matched when targetting phoneOS and vice-versa.</div><div><br class=""></div><div>If you need to differentiate between versions of the OS, there are #if available(*) "macros" or simply NSAppKitVersion constants.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><span style="font-family: Palatino-Roman;" class="">* developers can and will still deploy to OS X for Yoze and El Cap</span></div></div></div></div></blockquote><div><br class=""></div><div>Sure, but with Xcode 8 and Swift 3, the SDK will still be for macOS 10.12, so it could simply say #if os(macos), even when targetting prior OSs.</div><div><br class=""></div><div>All, of course, unless you want to apply these changes to Swift 2.x as well.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><span style="font-family: Palatino-Roman;" class=""><br class=""></span></div><div class=""><span style="font-family: Palatino-Roman;" class="">-- Erica</span></div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><br class=""></div></div></div></div><div class=""><blockquote type="cite" class=""><div class="">On Jun 16, 2016, at 8:29 AM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Starting in Sierra, Apple's Mac-based OS is renamed to macOS.</div><div class=""><br class=""></div><div class="">All user-facing Swift APIs must go through Swift Evolution. While this is a trivial API change, I have put together a formal proposal as is normal and usual for this process. Here is a draft for public comment.</div><div class=""><br class=""></div><div class=""> -- Erica</div><div class=""><br class=""></div>Gist: <a href="https://gist.github.com/erica/f53fa6cfef9e5cf17ab139f7528edde2" class="">https://gist.github.com/erica/f53fa6cfef9e5cf17ab139f7528edde2</a><div class=""><br class=""></div><div class=""><h1 style="box-sizing: border-box; font-size: 2.25em; margin-right: 0px; margin-bottom: 16px; margin-left: 0px; line-height: 1.2; padding-bottom: 0.3em; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: rgb(238, 238, 238); color: rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, 'Segoe UI', Arial, freesans, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; background-color: rgb(255, 255, 255); margin-top: 0px !important;" class="">Aliasing the OS X Platform Configuration Test</h1></div></div></div></blockquote></div></div></div></blockquote></div></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>