Lists

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

Re: Why do I receive KVO notification when new value IS the old value?

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

Re: Why do I receive KVO notification when new value IS the old value?

Subject: Re: Why do I receive KVO notification when new value IS the old value?
From: Greg Guerin <email@hidden>
Date: Wed, 8 Jul 2009 15:17:22 -0700

Jerry Krinock wrote:

This happens not only when the new and old values are -isEqual:, but when they are identically the same pointer. I can't think of any reason why anyone would want notification of a no-op.

What if the operation isn't a no-op? What if the operation represented some kind of accumulation instead of replacement, or an incremental change instead of assignment?

  -- GG

_______________________________________________

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


Follow-Ups:

Re: Why do I receive KVO notification when new value IS the old 	value?
From: BJ Homer <email@hidden>


Prev by Date:
Re: Core Data Material Properties

Next by Date:
Re: Why do I receive KVO notification when new value IS the old 	value?

Previous by thread:
Re: Why do I receive KVO notification when new value IS the old	value?

Next by thread:
Re: Why do I receive KVO notification when new value IS the old 	value?

Index(es):

Date
Thread