• 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: Is this good programming?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is this good programming?


  • Subject: Re: Is this good programming?
  • From: j o a r <email@hidden>
  • Date: Thu, 23 Aug 2007 15:09:03 +0200


On 23 aug 2007, at 14.38, Frank Bettger wrote:

My fault, there is no dangar because NSCalendarDates are always immutable.
However had they been mutable then my concern would be valid? Because then
the caller could change date (and therby entryDate) without calling one of
objects methods.


True, that can be a problem. You often use "copy" rather than "retain" in the setter for that reason.

j o a r


Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Is this good programming? (From: "Frank Bettger" <email@hidden>)
 >Re: Is this good programming? (From: j o a r <email@hidden>)
 >Re: Is this good programming? (From: "Frank Bettger" <email@hidden>)

  • Prev by Date: combining NSBezierPath
  • Next by Date: Re: combining NSBezierPath
  • Previous by thread: Re: Is this good programming?
  • Next by thread: Informing one class about another class's methods
  • Index(es):
    • Date
    • Thread