Do you have a source for this? While I bet there is research showing that 
acronyms on their own are easier to read in all caps, does it talk about when 
it is joined with other words such as urlHandler?

And like I said, just because ObjC devs are used to it is probably not a good 
enough rationale to overturn an accepted proposal. 

Brandon

Sent from my iPad

> On May 19, 2016, at 1:17 PM, Krystof Vasa <[email protected]> wrote:
> 
> Aside from ObjC developers being used to this, psychology of reading tells us 
> that people read by shapes of the words - they are used to seeing 
> abbreviations in capital letters - from this point, it's better readable.
> 
>> On May 19, 2016, at 7:14 PM, Brandon Knope via swift-evolution 
>> <[email protected]> wrote:
>> 
>> Do you have a particular reason? I don't think because it is a certain way 
>> in Objective-C means it must be that same way in Swift. 
>> 
>> Brandon 
>> 
>> Sent from my iPad
>> 
>>> On May 19, 2016, at 1:04 PM, Pavel Kapinos via swift-evolution 
>>> <[email protected]> wrote:
>>> 
>>> Hi,
>>> 
>>> SE-0005 "Better Translation of Objective-C APIs Into Swift Proposal” in 
>>> Proposed Solution # 6 "Lowercase values" suggests “to lowercase 
>>> non-prefixed values whenever they are imported” with an example of 
>>> URLHandler property becoming urlHandler. Being long time Cocoa developer, I 
>>> object to this particular example and would like to suggest to keep 
>>> capitalized any well known acronyms, like ASCII, PDF, URL etc. as they are 
>>> now in Cocoa. Thank you!
>>> 
>>> Cheers,
>>> Pavel.
>>> _______________________________________________
>>> swift-evolution mailing list
>>> [email protected]
>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>> _______________________________________________
>> swift-evolution mailing list
>> [email protected]
>> https://lists.swift.org/mailman/listinfo/swift-evolution
> 
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to