.Net style, but using ALL CAPS when the whole name is the acronym. Examples:
GC<Foo> MyGc<Bar> ARC<int> XML XmlNode HTTP XmlHttpRequest Reasoning: 1. All caps acronyms are a well known typographical convention. 2. UpperCamelCase has a constraint: word boundaries are recognized by case change. This constraint makes the concatenation of two acronyms unclear. That's why you end up with names like XMLHttpRequest() while using the impossible (IMO) Java style. My suggestion allows us to use the nice typographical typographical convention (1) and have a plan to avoid the problems caused by UpperCamelCase limitation (2). I guess this style would minimize the changes needed in the code base. -- Felipe Carvalho On Aug 2, 2013 10:29 PM, "Patrick Walton" <pwal...@mozilla.com> wrote: > Hi everyone, > > Brendan Eich emailed me expressing a preference for `GC<>` over `Gc<>`. I > think now is as good a time as any to have the bikeshedding debate :) > > I've noticed two styles for acronyms in type names: Java style > (HTTPServer) versus .NET style (HttpServer). Currently we are usually using > .NET style, but inconsistently (e.g. ARC). We never really decided. > > Here are a few examples of types in each style: > > * Java style: GC<Foo>, ARC<int>, SimpleHTTPServer, XMLHTTPRequest. > > * .NET style: Gc<Foo>, Arc<int>, SimpleHttpServer, XmlHttpRequest. > > I slightly prefer Java style myself because I think "GC" looks better than > "Gc", because Web APIs use Java style, and because Python does (e.g. > SimpleHTTPServer) and in general we've been following PEP 8. But I don't > feel strongly on this issue. > > Thoughts/straw poll? > > Patrick > ______________________________**_________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/**listinfo/rust-dev<https://mail.mozilla.org/listinfo/rust-dev> >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
