Re: NSAppKitVersionNumber wrong on latest Big Sur versions?!

2023-01-06 Thread Sean McBride via Cocoa-dev
On 6 Jan 2023, at 16:27, Rob Petrovec wrote: > Yes, this is a bug that started in 11.7 that doesn’t appear to have been > fixed yet in 11.7.2. Thanks for the confirmation. Sad that such a serious regression wasn't fixed in 11.7.1 nor 11.7.2. > Have you tried the arguably more robust and less

NSAppKitVersionNumber wrong on latest Big Sur versions?!

2023-01-06 Thread Sean McBride via Cocoa-dev
Hi all, On at least 3 Macs in my office, running macOS 11.7 or 11.7.2, NSAppKitVersionNumber (at runtime) is 2202.7 (sic). This conflicts with NSApplication.h which has: static const NSAppKitVersion NSAppKitVersionNumber11_0 = 2022; static const NSAppKitVersion NSAppKitVersionNumber11_1 =

Re: dispatch_apply() on an NSArray and Thread Sanitizer

2022-04-25 Thread Sean McBride via Cocoa-dev
Well, to close this thread, for anyone curious... I've tried on the same Mac, with the same Xcode version (13.2.1), on both macOS 11.6.6 vs 12.3.1, and it seems to be the OS that makes the difference. On 11, TSan correctly gives no error; but on 12 it gives this incorrect error about there

Re: dispatch_apply() on an NSArray and Thread Sanitizer

2022-04-19 Thread Sean McBride via Cocoa-dev
On 19 Apr 2022, at 19:35, Rob Petrovec wrote: > The docs for NSEnumerationConcurrent state that it is a hint and may be > ignored at run time. Ah, so they do. I had only checked in the header file. OK, one less mystery. Sean ___ Cocoa-dev mailing

Re: dispatch_apply() on an NSArray and Thread Sanitizer

2022-04-19 Thread Sean McBride via Cocoa-dev
On 19 Apr 2022, at 18:47, Saagar Jha wrote: If Thread Sanitizer says your code has a race, it almost certainly has a race. Yeah, that's been my general experience until now. Your simple code seems OK superficially, but there are a couple things that could be problematic here: either your

dispatch_apply() on an NSArray and Thread Sanitizer

2022-04-19 Thread Sean McBride via Cocoa-dev
Hi all, If one wants to do something with every item in an NSArray in a concurrent way, is the following safe/correct? NSArray* array = @[@5, @6, @7, @8, @9, @10, @11]; dispatch_apply([array count], DISPATCH_APPLY_AUTO, ^(size_t idx) { id unused = array[idx]; }); Here of

Re: NSPredicate: Using NSExpression CAST(x, 'Class') is deprecated and will be removed in a future release

2022-03-16 Thread Sean McBride via Cocoa-dev
On 18 Nov 2021, at 19:44, Sean McBride via Cocoa-dev wrote: > Hi all, > > Starting in Monterey, I see a new message logged by Core Data during > persistent store migration: > > NSPredicate: Using NSExpression CAST(x,'Class') is deprecated and will be > removed in a future

NSPredicate: Using NSExpression CAST(x, 'Class') is deprecated and will be removed in a future release

2021-11-18 Thread Sean McBride via Cocoa-dev
Hi all, Starting in Monterey, I see a new message logged by Core Data during persistent store migration: NSPredicate: Using NSExpression CAST(x,'Class') is deprecated and will be removed in a future release. 'MyClassName' should not be cast into a Class object.' This is due to my .xcmapping

Re: How to check signature and notarization?

2021-04-12 Thread Sean McBride via Cocoa-dev
On Mon, 12 Apr 2021 18:36:12 +0200, Gabriel Zachmann via Cocoa-dev said: >Is there a way to check that the signature and notarization is proper? >Are there any other checks I can do to determine what is going wrong? You might find this helpful:

Re: Thoughts on ARC

2019-10-02 Thread Sean McBride via Cocoa-dev
On Wed, 2 Oct 2019 10:50:19 +1300, Sam Ryan via Cocoa-dev said: >That was a good read, thank you for passing that on. It highlights a good >point, that Apple is itself releasing applications with non-Mac UI (News, >Home, Stocks, Voice Memos are mentioned in that article). Another way to look at