<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="">The reason is that Foundation on darwin re-exports modules below it (by the virtue of objective-c headers) and the linux version is not re-exporting Glibc.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 14, 2016, at 8:44 AM, Drew Crawford via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@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="">on Darwin, we can say:<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">import Foundation</div><div class="">exit(2)</div></blockquote><br class=""><div class="">I'm not totally sure how this works, since exit is provided by Darwin, not by Foundation. But somehow importing Foundation imports Darwin as well.</div><div class=""><br class=""></div><div class="">I think for source compatibility, we should support this, because <a href="http://stackoverflow.com/questions/34186994/swift-2-2-on-linux-use-of-unresolved-identifier-exit" class="">people</a> are <a href="http://stackoverflow.com/questions/24102157/seeking-an-exit-equivalent-in-swift" class="">asking</a> why it doesn't work out of the box.</div><div class=""><br class=""></div><div class="">I considered PRing an exit implementation in corelibs-foundation, but I think that might cause the opposite problem–introduce a conflict between Darwin/Glibc exit and Foundation "exit".</div><div class=""><br class=""></div><div class="">Can someone speak to how this is solved in Darwin Foundation and what we should do about it?</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=0mkChau6XnFV-2FCNUik62L9ZaldD0W0ziOwj-2F3jLx36-2FPkxfyxUPS-2Fvx8MtmbN5b5xt4LUDCJuud2DJ6qeVM-2FArlE8reS9lUsKmZGqibO35X8n5uUvqZUtvCakGYaKGF5Yuh7nXMLVFu5-2B92bkhVyIkWr-2F-2Bgik41BespjvEbXitUI1VSq0zJvtjyus0CCDiCJ4ColcoZ1yxfyxA66rLgo3WqLFTq8XDBCJBOHewrfzbU-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<br class="">swift-corelibs-dev mailing list<br class=""><a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev<br class=""></div></blockquote></div><br class=""></div></body></html>