<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;">I am still not clear how os_log is supposed to be used with Swift if you are not one of the elected ones that can ride his white horse straight into iOS 10+ only land of apps ;). In Objective-C I can use a macro, as wrapper functions are banned, but in Swift? Are availability checks every time I log the answer?</div><br>Sent from my iPhone</div><div><br>On 3 Sep 2016, at 17:28, Jean-Daniel Dupas via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><span></span><br><blockquote type="cite"><span>Le 3 sept. 2016 à 06:43, Georgios Moschovitis via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> a écrit :</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Can it be corrected in Swift 4 (breaking changes etc…)?</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Good question.</span><br></blockquote><blockquote type="cite"><span>Maybe the core team should accept additional source-breaking changes in 3.x releases?</span><br></blockquote><span></span><br><span></span><br><span>I think the framework API mapping itself is not part of the language and is handle by Apple directly (at least for Apple specifics frameworks). I don’t know if such changes are subject to the same policy.</span><br><span></span><br><span></span><br><span></span><br><span></span><br><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>