<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 Dec 5, 2015, at 12:25 PM, Gage Morgan via swift-lldb-dev <<a href="mailto:swift-lldb-dev@swift.org" class="">swift-lldb-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">As your question is similar to the one I have, does Apple explicitly say what we can and cannot do with REPL on Linux?<br class=""><br class=""></div></div></blockquote><div><br class=""></div><div><div class="">Hi Gage,</div><div class=""><br class=""></div><div class="">Great question! <a href="http://swift.org" class="">Swift.org</a> was setup to encourage collaboration and expansion of the Swift ecosystem, both in terms of platform and feature set. Community contributions to expand usage of the REPL in new and novel ways is encouraged, whether it be to support a new platform, a new windowing mechanism or to incorporate in a program as an extension language. Apple is not attempting to limit the scope of community contributions; rather, we’re explicitly encouraging it by open sourcing Swift.</div><div class=""><br class=""></div><div class="">You are welcome to take any part of the REPL and modify and/or incorporate into your program. The <a href="http://swift.org" class="">swift.org</a> and <a href="http://llvm.org" class="">llvm.org</a> licenses just ask that you attribute the code borrowed (per their licenses) in your product. Go forth and make great things :-)</div><div class=""><br class=""></div><div class="">Sincerely,</div><div class="">Todd Fiala</div><div class=""><br class=""></div></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div class="acompli_signature">Sent from <a href="http://aka.ms/Ox5hz3" class="">Outlook</a></div><br class=""></div><img src="https://u2002410.ct.sendgrid.net/wf/open?upn=32vpTPxAlXAtmcvTFkUUhNE6AUvUiUhYc68jZ5NFztpncH6Eg9NvTx1jQYZRLrnn-2FYA6n67ZgudwgiBq-2FKLrCSZrE0w8t7oM1-2F9amxUBH-2BjgkYHXdr1MVNNzoaJ5L-2FZINgeK-2B-2Foj-2FX7b5bCC79VgLnR1lKtq4270UbMiXiu3lfRp-2BrQ4w4ot8Q0U-2FeEVXbaLoLQDGFwaDenPEI8gcYHYMbG-2BIK695qRqTurjHc1hWSs-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="">
_______________________________________________<br class="">swift-lldb-dev mailing list<br class=""><a href="mailto:swift-lldb-dev@swift.org" class="">swift-lldb-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-lldb-dev<br class=""></div></blockquote></div><br class=""></body></html>