On 18 juil. 2018, at 09:27, Quinn The Eskimo! wrote:
> Why are you building with the 10.8 SDK? I understand that it can take time > to move forward to new tools, but 10.9 is five years old now. The longer you > stay on the old SDKs, the further off the beaten path you end up, and this is > just one example of the various land mines waiting for you out there. The problem with using the most recent SDKs (assuming your hardware can run recent macOS version and Xcode) is that this is also a situation for numerous land mines such as: - APIs not existing on previous OS versions and no warnings during build. - backward compatibility bugs in Xcode, AppKit: e.g. settings a NSTextField text color to labelColor will crash an app on 10.6 at least and yet it's still allowed when you specify the deployment target to be 10.6 or later. - finding out that some stuff is not working the same way depending on the OS versions (e.g. ViewControllers being part of the responder chain or not). - finding out that some behavior is not the same when you link with a recent version of the SDK instead of the one you are used to. And these kinds of issues are more difficult to investigate that spending time supporting new APIs using if ([ respondsToSelector:]==YES) [ performSelector: withObject:]; (Of course, this assumes Obj-C, I'm not sure whether forward compatibility is supported in Swift). Personally, I would also add that the Cocoa Obj-C headers in more recent SDKs are becoming less and less legible due to all the stuff that has been added to help the Swift toolchain. _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
