Re: Mutable class problems
Re: Mutable class problems
- Subject: Re: Mutable class problems
- From: Mike Shields <email@hidden>
- Date: Mon, 24 Jun 2002 22:36:25 -0600
Why not save yourself the hassle and simply always return another
dictionary of results? I seem to remember a conversation where checking
for immutablity was bound to fail in some obscure way.
Mike
On Monday, June 24, 2002, at 09:47 PM, Rosyna wrote:
The dictionary contains a set of NSNumbers. If the input is Mutable, I
will use and perform calculations on the numbers and use it if it is
not NULL. If the collection is immutable, I will check to see if it is
NULL and then create a new dictionary. If it is not NULL and immutable
I return paramErr.
Ack, at 6/24/02, John C. Randolph said:
Generally speaking, what you should be doing is making a -copy or a
-mutableCopy of the given collection, depending on what you need it
to be.
How about filling us in on what you're doing?
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
---
Please include any previous correspondence in replies, it helps me
remember what we were talking about. Thanks.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.