关于NSDateFormatter的线程安全问题

最新推荐文章于 2023-02-20 17:01:41 发布

zskm001

最新推荐文章于 2023-02-20 17:01:41 发布

阅读量824

点赞数

分类专栏：菜鸟成长文章标签：线程安全 NSDateFormatter

本文链接：https://blog.csdn.net/zskm001/article/details/51883076

版权

菜鸟成长专栏收录该内容

5 篇文章 0 订阅

订阅专栏

今天闲逛，突然捕获一个帖子说NSDateFormatter线程不安全，为了线程安全最好每个线程用自己的对象，如果需要用到的话

NSMutableDictionary *threadDictionary = [[NSThread currentThread] threadDictionary];
NSDateFormatter *dateFormatter = threadDictionary[@”mydateformatter”];
if(!dateFormatter){
@synchronized(self){
if(!dateFormatter){
dateFormatter = [[NSDateFormatter alloc] init];
[dateFormatter setDateFormat:@”yyyy-MM-dd HH:mm:ss”];
[dateFormatter setTimeZone:[NSTimeZone timeZoneWithName:@”Asia/Shanghai”]];
threadDictionary[@”mydateformatter”] = dateFormatter;
}
}
}
然后看了看文档，发现线程安全问题已经基本解决了：

https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSDateFormatter_Class/index.html#//apple_ref/occ/cl/NSDateFormatter

Thread Safety

On iOS 7 and later NSDateFormatter is thread safe.

On OS X 10.9 and later NSDateFormatter is thread safe so long as you are using the modern behavior in a 64-bit app.

On earlier versions of the operating system, or when using the legacy formatter behavior or running in 32-bit on OS X, NSDateFormatter is not thread safe, and you therefore must not mutate a date formatter simultaneously from multiple threads.

想不到兜了个圈，又回来了，不过能多了解点知识总是好的~~~