I regularly work with Linux and am quite comfortable with case sensitive file systems, but I wouldn’t ever use the same name differing only in case in the same directory. To me, file names or variable names should be meaningful independent of case. Of course, with the language we have the convention on using cases that imply what something is. That is a good thing. For me, the case is used more often to add clarity of meaning than to resolve different entities with the same name except for case. Using “Self” and “self” is certainly consistent with the language rules and naming convention, but not something I think should be encouraged.
On Apr 21, 2016, at 1:10 AM, L Mihalkovic <firstname.lastname@example.org<mailto:email@example.com>> wrote:
I couldn't understand for a moment why people would think that “Self" versus "self” is confusing.. and then I remembered that Apple does not (by default) distinguish file names with different casing in the filesystem… I think we either educate people or we keep them ignorant in the name of their best interest. Apple seem to regularly choose the bottom end. I hope after 40 years someone will decide it is time to look forward and embrace Self
On Apr 21, 2016, at 3:14 AM, Brent Royal-Gordon via swift-evolution <firstname.lastname@example.org<mailto:email@example.com>> wrote:
1) “Self" differs from “self” by just the first letter being capitalized. Regardless of case, it is confusing for the terms “self” or “Self” or “SELF” to mean different things from within the same context.
What, you've never done things like this?
let page = Page()
let document = Document(pages: [page])
let account = Account(oAuthToken: token)
Sent from my iPhone
swift-evolution mailing list