Re: [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")

I would support Option 3. Neither iPad nor NeXT are acronyms, so they needn’t fall under the same rule. Rule A: Acronyms all lowercase, all uppercase URL -> urlString, URLRequest LaTeX -> latexSource, LATEXRenderer GIF -> gifRepresentation, GIFGenerator Rule B: Brand names all lowercase, first

Re: [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")

Terminology-wise, most of these are not acronyms (or initialisms ), but you’re right that that’s a third option consistent with the existing guidelines. Jordan > On May 5, 2016, at 08:56, Basem Emara

Re: [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")

Sent from my iPad > On May 5, 2016, at 10:41 AM, Jordan Rose via swift-evolution > wrote: > > [resending to include list] > > Hm. I’m not sure why these words would be special, though—if we were going to > use underscores, shouldn’t we consistently go for

Re: [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")

Yes I digress and agree with you consistency is absolute key. Another thought came to mind: Option 3 3: Uppercase all acronyms including those with mixed casing. This is both consistent and clear. Isolating acronyms is important because they loose their meaning and bleed into word boundaries,

Re: [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")

[resending to include list] Hm. I’m not sure why these words would be special, though—if we were going to use underscores, shouldn’t we consistently go for “snake_case” or something? (A leading underscore is also often used to denote something private in a lot of conventions, including the

[swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")

Following my current cpp guidelines, I would suggest the following: 1. Make all letters of the abbreviation downcase 2. Make first letter uppercase if required Examples: NanWrapper, getNan, nanGet, NextEmulator, emulateNext, nextEmulate. Although, this convention plays pretty hard on NeXT, I

Re: [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")

> On May 5, 2016, at 10:26 AM, Jordan Rose via swift-evolution > wrote: > > (“NeXT” is an especially tricky case because without case it’s not > distinguishable from the normal word “next”. This situation is rare but not > nonexistent. Then again, “Apple” is not