In the original example, myNum was being passed as a argument rather
than having a message to sent to it and itÂ’s often not safe to pass
nil objects as arguments.

Hmmm... well, what's the function it's passed to going to do with it,
other than call a method on it? If it's doing anything else, it's
breaking other (much stronger) rules.

Okay, so question 2: what else could be done other than calling methods on it? I'm using NSNumbers in place of ints, floats and so on partly as a learning exercise and partly to make it easier to convert the number types rather than casting them. The library I had put together (which was just an object with no instance variables) originally used all floats (it's a math heavy library).

Ashley_______________________________________________

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 [EMAIL PROTECTED]

Reply via email to