• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Core Data/Cocoa Bindings: best practice for using strings in code?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data/Cocoa Bindings: best practice for using strings in code?


  • Subject: Re: Core Data/Cocoa Bindings: best practice for using strings in code?
  • From: mmalcolm crawford <email@hidden>
  • Date: Wed, 13 Jul 2005 13:55:44 -0700


On Jul 13, 2005, at 1:43 PM, Michael McCracken wrote:

Hi, using Core Data and Cocoa Bindings, I find that my code is lousy
with string constants for things like entity names and key paths. I've
already had one typo that wasn't immediately obvious, and that's
enough. I'm thinking about solving this by defining them all as cpp
macros, but that seems like a maintenance headache (although still an
improvement) as I experiment with the data model.

Many developers define string constants for the keys.
You can also implement custom classes with specific accessor methods.

mmalc

_______________________________________________
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: 
 >Core Data/Cocoa Bindings: best practice for using strings in code? (From: Michael McCracken <email@hidden>)

  • Prev by Date: Re: C string conversions?
  • Next by Date: Re: Core Data/Cocoa Bindings: best practice for using strings in code?
  • Previous by thread: Core Data/Cocoa Bindings: best practice for using strings in code?
  • Next by thread: Re: Core Data/Cocoa Bindings: best practice for using strings in code?
  • Index(es):
    • Date
    • Thread