are nsstrings internally locked?
are nsstrings internally locked?
- Subject: are nsstrings internally locked?
- From: Philip George <email@hidden>
- Date: Tue, 22 Jul 2003 18:40:19 -0500
I'm doing a ton of nslocking on multiple threads for fear of caching a
partial nsmutablestring from one thread while another was trying to modify
it. Should I be worried about this? Are nsstring/nsmutablestring objects
locked internally? I have yet to actually SEE with my own two eyes an
NSMutableString get interrupted by another thread while being modified with
the setString: method, but that's no proof that it couldn't happen.
Anyone know for sure?
I'd love to not have to write all this extra locking code if it were
possible. :)
Thanks.
- Philip
_______________________________________________
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.