Open sn0 opened 9 years ago
Thanks for this, @sn0! I was looking at this today myself, but I'm hesitant to merge it into master because I use this category in several iOS and OS X projects that support system versions prior to iOS 8 and OS X 10.10. I'd like to quiet the warnings, but not ignore them, but also not break compatibility (yet). Telling Xcode to ignore the warnings seems like a bad idea, but I could add a single #warning directive to remind us that for the time being we are using deprecated symbol names here.
What do you think?
That's a good point. I didn't think about compatibility. A single warning sounds good to me.
Just update calls which became deprecated in iOS8