On Aug 24, 2009, at 3:45 AM, Greg Parker wrote:
On Aug 23, 2009, at 8:12 PM, Adam R. Maxwell wrote:On Aug 23, 2009, at 8:01 PM, Kyle Sluder wrote:On Aug 23, 2009, at 7:42 PM, PCWiz <pcwiz.supp...@gmail.com> wrote:name:@"NSFileHandleReadCompletionNotification"NSFileHandleReadCompletionNotification is the name of a constant, not necessarily its value.Right, and that was my first thought, too! I've never used NSFileHandle for this purpose, either, so wrote a quick test app to see what would happen. It turns out that the value is the same as the constant in this case, thoughDoesn't matter. Use the framework-provided constant. Some code depends on seeing the same address as the framework's variable. Such code will fail if you use a different copy of the same characters.
IIRC there's some limitation with NSNotification and constants, but I couldn't find it in the documentation last time I checked. Doesn't NSNotificationQueue coalescing depend on pointer equality of the notification name? Regardless, I always use named constants, as you say, and had no intention to contradict Kyle's advice there.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
