<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="">For swift stuff I thought the prefix was being dropped (except for bleeding through from Obj-C).<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 2016-02-12, at 21:25:51, Xiaodi Wu via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="white-space:pre-wrap" class="">Sorry, by vendor prefix I mean the NS in NSArray, or AV in AVURLAsset, etc. Does #2 mean that we are to have AvUrlAsset? Or AVUrlAsset?</div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Fri, Feb 12, 2016 at 4:20 AM Dave Abrahams via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
on Fri Feb 12 2016, Xiaodi Wu &lt;<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>&gt; wrote:<br class="">
<br class="">
&gt; Based on the examples, #2 does seem to have the most advantages. But:<br class="">
&gt; what to do with vendor prefixes? Are those to be an exception?<br class="">
<br class="">
Can you some examples of a “vendor prefix?”<br class="">
<br class="">
&gt; Another tidbit: .NET seems to have its own exceptions--not sure if<br class="">
&gt; there are rules for them, but just at the namespace level there's<br class="">
&gt; System.IO and UIAutomationClientsideProviders, spelled as shown.<br class="">
<br class="">
Thanks for pointing those out.<br class="">
<br class="">
&gt;<br class="">
&gt;<br class="">
&gt; On Fri, Feb 12, 2016 at 3:07 AM, Dave Abrahams via swift-evolution<br class="">
&gt; &lt;<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>&gt; wrote:<br class="">
&gt;&gt;<br class="">
&gt;&gt; on Fri Feb 12 2016, Rob Mayoff &lt;<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>&gt; wrote:<br class="">
&gt;&gt;<br class="">
&gt;&gt;&gt; I have been using #2 for years in many languages (including Objective-C and<br class="">
&gt;&gt;&gt; more recently Swift) and much prefer it.<br class="">
&gt;&gt;&gt;<br class="">
&gt;&gt;&gt; Incidentally, "ASCII" is one of the examples in the definition of "acronym"<br class="">
&gt;&gt;&gt; in OS X's American English dictionary.<br class="">
&gt;&gt;<br class="">
&gt;&gt; Yup, you're right.<br class="">
&gt;&gt;<br class="">
&gt;&gt;&gt; On Thu, Feb 11, 2016 at 11:51 PM, Dave Abrahams via swift-evolution &lt;<br class="">
&gt;&gt;&gt; <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>&gt; wrote:<br class="">
&gt;&gt;&gt;&gt;<br class="">
&gt;&gt;&gt;&gt; I just posted a write-up about various case conventions for initialisms:<br class="">
&gt;&gt;&gt;&gt; <a href="https://gist.github.com/dabrahams/55fc5ece355da4664730" rel="noreferrer" target="_blank" class="">https://gist.github.com/dabrahams/55fc5ece355da4664730</a>.&nbsp; I was surprised<br class="">
&gt;&gt;&gt;&gt; at how it turned out, FWIW.<br class="">
&gt;&gt;&gt;&gt;<br class="">
&gt;&gt;&gt; _______________________________________________<br class="">
&gt;&gt;&gt; swift-evolution mailing list<br class="">
&gt;&gt;&gt; <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
&gt;&gt;&gt; <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
&gt;&gt;<br class="">
&gt;&gt; --<br class="">
&gt;&gt; -Dave<br class="">
&gt;&gt;<br class="">
&gt;&gt; _______________________________________________<br class="">
&gt;&gt; swift-evolution mailing list<br class="">
&gt;&gt; <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
&gt;&gt; <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
&gt; _______________________________________________<br class="">
&gt; swift-evolution mailing list<br class="">
&gt; <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
&gt; <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class="">
--<br class="">
-Dave<br class="">
<br class="">
_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</blockquote></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=""></div></body></html>