[swift-evolution] Analysis of case conventions for initialisms

[Craig Cruden]

For swift stuff I thought the prefix was being dropped (except for bleeding through from Obj-C).

> On 2016-02-12, at 21:25:51, Xiaodi Wu via swift-evolution <swift-evolution at swift.org> wrote:
> 
> 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?
> 
> On Fri, Feb 12, 2016 at 4:20 AM Dave Abrahams via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> 
> on Fri Feb 12 2016, Xiaodi Wu <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> 
> > Based on the examples, #2 does seem to have the most advantages. But:
> > what to do with vendor prefixes? Are those to be an exception?
> 
> Can you some examples of a “vendor prefix?”
> 
> > Another tidbit: .NET seems to have its own exceptions--not sure if
> > there are rules for them, but just at the namespace level there's
> > System.IO and UIAutomationClientsideProviders, spelled as shown.
> 
> Thanks for pointing those out.
> 
> >
> >
> > On Fri, Feb 12, 2016 at 3:07 AM, Dave Abrahams via swift-evolution
> > <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> >>
> >> on Fri Feb 12 2016, Rob Mayoff <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> >>
> >>> I have been using #2 for years in many languages (including Objective-C and
> >>> more recently Swift) and much prefer it.
> >>>
> >>> Incidentally, "ASCII" is one of the examples in the definition of "acronym"
> >>> in OS X's American English dictionary.
> >>
> >> Yup, you're right.
> >>
> >>> On Thu, Feb 11, 2016 at 11:51 PM, Dave Abrahams via swift-evolution <
> >>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> >>>>
> >>>> I just posted a write-up about various case conventions for initialisms:
> >>>> https://gist.github.com/dabrahams/55fc5ece355da4664730 <https://gist.github.com/dabrahams/55fc5ece355da4664730>.  I was surprised
> >>>> at how it turned out, FWIW.
> >>>>
> >>> _______________________________________________
> >>> swift-evolution mailing list
> >>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> >>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> >>
> >> --
> >> -Dave
> >>
> >> _______________________________________________
> >> swift-evolution mailing list
> >> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> >> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> > https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 
> --
> -Dave
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160212/ff038abd/attachment.html>