On Jan 27, 2016, at 6:38 AM, Dave wrote: > >>> >>>> I'm going to step out on a limb and since Xcode has supported editing in >>>> UTF-8 and 16, that we look into those character sets and pick some symbols >>>> that accurately represent public, protected and private. >>> >>> Now you’re pulling our legs, right Alex? >> >> Yeah, I know. It's really non conventional, buuut… I've started using some >> of the characters such as the block and non breaking line to make better >> formatting for comments and logging. > > Wow Man, you *do* like living on the wild-side. I hope it doesn’t come back > to bite you!
Wise words. I base this attempt on a fair amount of crash test dummies who have risked this before me and constantly asking questions. Is the character set supported by Xcode? By Git? The popups in the right side of Inspector Panel with a setting for Text Encoding and the amount of people who I've seen code in Japanese with the UTF-16 encoding justified me asking this. But for those crazy Swift kids who are using smilies in variable names, I'm going to let them drive the crash test vehicle. >> Other people who are on the Swift side of things are even using smilies and >> emoticons in their code. Or so they claim. That scares me. > > I’m more of a if its not in the ASCII set it ain’t Source Code brigade! lol > > All the Best > Dave _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
