Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: CoreData Entity attributes vs. Cocoa naming conventions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData Entity attributes vs. Cocoa naming conventions

Subject: Re: CoreData Entity attributes vs. Cocoa naming conventions
From: Scott Stevenson <email@hidden>
Date: Mon, 7 Nov 2005 14:29:03 -0800


On Nov 7, 2005, at 11:33 AM, Jim Correia wrote:

Obviously this isn't the end of the world, but setUrlString: is uglier than setURLString:. Is the UI being overzealous, or enforcing a hard requirement down inside the frameworks? (Or should I just get over it - as I have had to do - and just give my accessor and attribute the "ugly" name? :-)

The path of least resistance -- choose a descriptive adjective to go in front of the "URLString" attribute name. :)

     - Scott

--
http://theocacao.com/


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



References:  
  >CoreData Entity attributes vs. Cocoa naming conventions (From: Jim Correia <email@hidden>)




Prev by Date:
CFUserNotificationCreate does not work from daemon started via	launchd

Next by Date:
Re: CFUserNotificationCreate does not work from daemon started	via	launchd

Previous by thread:
CoreData Entity attributes vs. Cocoa naming conventions

Next by thread:
Re: CoreData Entity attributes vs. Cocoa naming conventions

Index(es):

Date
Thread