The language used for creating NSManagedObject (not MOC) subclasses is set in the data model’s file inspector. It defaults to Swift. Core Data data models also support automatic code generation, which

Sure, just use NSTask’s own standardInput, standardOutput, and standardError support with NSPipe. No need to tell the task to send its stdout to some intermediate file that your app then opens and rea

The document you cite is about Key Value Coding, not about Objective-C properties. The latter are not implemented using the former. If a @property declaration specifies a getter or setter method, the

There’s always the NSProcessInfo.operatingSystemVersion property. -- Chris

My first assumption with symptoms like this is that there’s something trying to do UI from a background thread. -- Chris

That should be reasonable, I don’t recall whether you’ll need to create a mapping model or not to actually migrate the existing store. It does mean that all of the instances will wind up shoved into a

If you put the entities themselves in an inheritance relationship, Xcode will generate code reflecting that. I would only do this for “strongly” related entities though since entity inheritance implie

In fact you don’t even need a new model version, you can just refactor the code. We made sure that Core Data’s concept of entity inheritance is independent of class hierarchy, so you don’t actually ne

I don’t have any detailed list of what changed in Xcode 9.3 that I can share, sorry. Speaking generally, the only changes anyone should notice should be positive; much of the underlying infrastructure

The main idea for Cocoa localization is that your source artifacts are the “the truth” for your development region (by default English): You use the real strings in NSLocalizedString() macros and in y

Create your own thread and give it a run loop, then use IORegisterForSystemPower on that run loop. -- Chris

Neither of these statements is correct: (1) File handles are per-process, not per-thread. It’s the developer’s responsibility not to try to manipulate the same file handle from multiple threads at the